-
Notifications
You must be signed in to change notification settings - Fork 9
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add support for Azure archival locations (#168)
- Loading branch information
1 parent
db58084
commit c6e12c9
Showing
9 changed files
with
457 additions
and
18 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,59 @@ | ||
--- | ||
# generated by https://github.com/hashicorp/terraform-plugin-docs | ||
page_title: "polaris_azure_archival_location Resource - terraform-provider-polaris" | ||
subcategory: "" | ||
description: |- | ||
The polaris_azure_archival_location resource creates an RSC archival location for cloud-native workloads. | ||
When creating an archival location, the region where the snapshots are stored needs to be specified: | ||
* Source Region - Store snapshots in the same region to minimize data transfer charges. This is the default behaviour when the storage_account_region field is not specified. | ||
* Specific region - Storing snapshots in another region can increase total data transfer charges. The storage_account_region field specifies the region. | ||
Custom storage encryption is enabled by specifying one or more customer_managed_key blocks. Each customer_managed_key block specifies the encryption details to use for a region. For other regions, data will be encrypted using platform managed keys. | ||
-> Note: The Azure storage account is not created until the first protected object is archived to the location. | ||
--- | ||
|
||
# polaris_azure_archival_location (Resource) | ||
|
||
The `polaris_azure_archival_location` resource creates an RSC archival location for cloud-native workloads. | ||
|
||
When creating an archival location, the region where the snapshots are stored needs to be specified: | ||
* *Source Region* - Store snapshots in the same region to minimize data transfer charges. This is the default behaviour when the `storage_account_region` field is not specified. | ||
* *Specific region* - Storing snapshots in another region can increase total data transfer charges. The `storage_account_region` field specifies the region. | ||
|
||
Custom storage encryption is enabled by specifying one or more `customer_managed_key` blocks. Each `customer_managed_key` block specifies the encryption details to use for a region. For other regions, data will be encrypted using platform managed keys. | ||
|
||
-> **Note:** The Azure storage account is not created until the first protected object is archived to the location. | ||
|
||
|
||
|
||
<!-- schema generated by tfplugindocs --> | ||
## Schema | ||
|
||
### Required | ||
|
||
- `cloud_account_id` (String) RSC cloud account ID. | ||
- `name` (String) Cloud native archival location name. | ||
- `storage_account_name_prefix` (String) Azure storage account name prefix. The storage account name prefix cannot be longer than 14 characters and can only consist of numbers and lower case letters. | ||
|
||
### Optional | ||
|
||
- `customer_managed_key` (Block Set) Customer managed storage encryption. Specify the regions and their respective encryption details. For other regions, data will be encrypted using platform managed keys. (see [below for nested schema](#nestedblock--customer_managed_key)) | ||
- `redundancy` (String) Azure storage redundancy. Possible values are `GRS`, `GZRS`, `LRS`, `RA_GRS`, `RA_GZRS` and `ZRS`. Default value is `LRS`. | ||
- `storage_account_region` (String) Azure region to store the snapshots in. If not specified, the snapshots will be stored in the same region as the workload. | ||
- `storage_account_tags` (Map of String) Azure storage account tags. Each tag will be added to the storage account created by RSC. | ||
- `storage_tier` (String) Azure storage tier. Possible values are `COOL` and `HOT`. Default value is `COOL`. | ||
|
||
### Read-Only | ||
|
||
- `connection_status` (String) Connection status of the cloud native archival location. | ||
- `container_name` (String) Azure storage container name. | ||
- `id` (String) Cloud native archival location ID. | ||
- `location_template` (String) RSC location template. If a storage account region was specified, it will be `SPECIFIC_REGION`, otherwise `SOURCE_REGION`. | ||
|
||
<a id="nestedblock--customer_managed_key"></a> | ||
### Nested Schema for `customer_managed_key` | ||
|
||
Required: | ||
|
||
- `name` (String) Key name. | ||
- `region` (String) The region in which the key will be used. Regions without customer managed keys will use platform managed keys. | ||
- `vault_name` (String) Key vault name. |
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.