-
Notifications
You must be signed in to change notification settings - Fork 16
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix: Fixed application segment match_style validation
- Loading branch information
Showing
12 changed files
with
186 additions
and
62 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,52 @@ | ||
--- | ||
page_title: "zpa_service_edge_assistant_schedule Data Source - terraform-provider-zpa" | ||
subcategory: "Service Edge Controller" | ||
description: |- | ||
Official documentation https://help.zscaler.com/zpa/deleting-disconnected-app-connectors | ||
documentation https://help.zscaler.com/zpa/configuring-auto-delete-disconnected-app-connectors-using-api | ||
Get information about ZPA Service Edge Controller Assistant Schedule in Zscaler Private Access cloud. | ||
--- | ||
|
||
# zpa_service_edge_assistant_schedule (Data Source) | ||
|
||
* [Official documentation](https://help.zscaler.com/zpa/deleting-disconnected-app-connectors) | ||
* [API documentation](https://help.zscaler.com/zpa/configuring-auto-delete-disconnected-app-connectors-using-api) | ||
|
||
Use the **zpa_service_edge_assistant_schedule** data source to get information about Auto Delete frequency of the Service Edge for the specified customer in the Zscaler Private Access cloud. | ||
|
||
~> **NOTE** - The `customer_id` attribute is optional and not required during the configuration. | ||
|
||
## Example Usage | ||
|
||
```terraform | ||
// Retrieve All Assistant Schedules | ||
data "zpa_service_edge_assistant_schedule" "this" {} | ||
// Retrieve A Specific Assistant Schedule by ID | ||
data "zpa_service_edge_assistant_schedule" "this" { | ||
id = "1" | ||
} | ||
// Retrieve A Specific Assistant Schedule by the Customer ID | ||
data "zpa_service_edge_assistant_schedule" "this" { | ||
customer_id = "1234567891012" | ||
} | ||
``` | ||
|
||
## Schema | ||
|
||
### Required | ||
|
||
The following arguments are supported: | ||
|
||
* `id` - (Number) The unique identifier for the Service Edge auto deletion configuration for a customer. This field is only required for the PUT request to update the frequency of the Service Edge Settings. | ||
* `customer_id` - (Number) The unique identifier of the ZPA tenant. | ||
|
||
### Read-Only | ||
|
||
In addition to all arguments above, the following attributes are exported: | ||
|
||
* `enabled` (Boolean) - Indicates if the setting for deleting Service Edge is enabled or disabled. | ||
* `delete_disabled` (Boolean) - Indicates if the Service Edge are included for deletion if they are in a disconnected state based on frequencyInterval and frequency values. | ||
* `frequency` (String) - The scheduled frequency at which the disconnected Service Edge are deleted. Supported value is: `days` | ||
* `frequency_interval` - (String) - The interval for the configured frequency value. The minimum supported value is 5. Supported values are: `5`, `7`, `14`, `30`, `60` and `90` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,61 @@ | ||
--- | ||
page_title: "zpa_service_edge_assistant_schedule Resource - terraform-provider-zpa" | ||
subcategory: "Service Edge Controller" | ||
description: |- | ||
Official documentation https://help.zscaler.com/zpa/configuring-app-connectors-settings | ||
documentation https://help.zscaler.com/zpa/configuring-auto-delete-disconnected-app-connectors-using-api | ||
Configures Auto Delete for the specified disconnected Service Edge. | ||
--- | ||
|
||
# zpa_service_edge_assistant_schedule (Resource) | ||
|
||
* [Official documentation](https://help.zscaler.com/zpa/configuring-app-connectors-settings) | ||
* [API documentation](https://help.zscaler.com/zpa/configuring-auto-delete-disconnected-app-connectors-using-api) | ||
|
||
Use the **zpa_service_edge_assistant_schedule** resource sets the scheduled frequency at which the disconnected Service Edges are eligible for deletion. The supported value for frequency is days. The frequencyInterval field is the number of days after an Service Edge disconnects for it to become eligible for deletion. The minimum supported value for frequencyInterval is 5. | ||
|
||
~> **NOTE** - When enabling the Assistant Schedule for the first time, you must provide the `customer_id` information. If you authenticated using environment variables and used `ZPA_CUSTOMER_ID` environment variable, you don't have to define the customer_id attribute in the HCL configuration, and the provider will automatically use the value from the environment variable `ZPA_CUSTOMER_ID` | ||
|
||
## Example Usage - Defined Customer ID Value | ||
|
||
```terraform | ||
resource "zpa_service_edge_assistant_schedule" "this" { | ||
customer_id = "123456789101112" | ||
frequency = "days" | ||
frequency_interval = "5" | ||
enabled = true | ||
delete_disabled = true | ||
} | ||
``` | ||
|
||
## Example Usage - Customer ID Via Environment Variable | ||
|
||
```terraform | ||
resource "zpa_service_edge_assistant_schedule" "this" { | ||
frequency = "days" | ||
frequency_interval = "5" | ||
enabled = true | ||
delete_disabled = true | ||
} | ||
``` | ||
|
||
## Schema | ||
|
||
### Required | ||
|
||
The following arguments are supported: | ||
|
||
- `customer_id` - (String) - When enabling the Assistant Schedule for the first time, you must provide the `customer_id` information. If you authenticated using environment variables and used `ZPA_CUSTOMER_ID` environment variable, you don't have to define the customer_id attribute in the HCL configuration, and the provider will automatically use the value from the environment variable `ZPA_CUSTOMER_ID` | ||
- `frequency_interval` - (String) - The interval for the configured frequency value. The minimum supported value is 5. Supported values are: `5`, `7`, `14`, `30`, `60` and `90` | ||
- `frequency` (String) - The scheduled frequency at which the disconnected Service Edges are deleted. Supported value is: `days` | ||
|
||
### Optional | ||
|
||
In addition to all arguments above, the following attributes are exported: | ||
|
||
- `enabled` (Boolean) - Indicates if the setting for deleting Service Edges is enabled or disabled. Supported values are: `true` or `false` | ||
- `delete_disabled` (Boolean) - Indicates if the Service Edges are included for deletion if they are in a disconnected state based on frequencyInterval and frequency values. Supported values are: `true` or `false` | ||
|
||
## Import | ||
|
||
Import is not currently supported for this resource. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.