Added - Support for KMS Cross Region Replication for Virtual Vaults

Author: Terraform Team Automation

internal/integrationtest/kms_vault_test.go

@@ -369,6 +369,7 @@ func TestKmsVaultResource_basic(t *testing.T) {
 				resource.TestCheckResourceAttr(singularDatasourceName, "display_name", "displayName2"),
 				resource.TestCheckResourceAttrSet(singularDatasourceName, "id"),
 				resource.TestCheckResourceAttrSet(singularDatasourceName, "is_primary"),
+				resource.TestCheckResourceAttrSet(singularDatasourceName, "is_vault_replicable"),
 				resource.TestCheckResourceAttrSet(singularDatasourceName, "management_endpoint"),
 
 				resource.TestCheckResourceAttrSet(singularDatasourceName, "state"),

internal/service/kms/kms_vault_data_source.go

@@ -94,6 +94,10 @@ func (s *KmsVaultDataSourceCrud) SetData() error {
 		s.D.Set("is_primary", *s.Res.IsPrimary)
 	}
 
+	if s.Res.IsVaultReplicable != nil {
+		s.D.Set("is_vault_replicable", *s.Res.IsVaultReplicable)
+	}
+
 	if s.Res.ManagementEndpoint != nil {
 		s.D.Set("management_endpoint", *s.Res.ManagementEndpoint)
 	}

internal/service/kms/kms_vault_resource.go

@@ -258,6 +258,10 @@ func KmsVaultResource() *schema.Resource {
 				Type:     schema.TypeBool,
 				Computed: true,
 			},
+			"is_vault_replicable": {
+				Type:     schema.TypeBool,
+				Computed: true,
+			},
 			"management_endpoint": {
 				Type:     schema.TypeString,
 				Computed: true,
@@ -555,6 +559,10 @@ func (s *KmsVaultResourceCrud) SetData() error {
 		s.D.Set("is_primary", *s.Res.IsPrimary)
 	}
 
+	if s.Res.IsVaultReplicable != nil {
+		s.D.Set("is_vault_replicable", *s.Res.IsVaultReplicable)
+	}
+
 	if s.Res.ManagementEndpoint != nil {
 		s.D.Set("management_endpoint", *s.Res.ManagementEndpoint)
 	}

website/docs/d/kms_key.html.markdown

@@ -41,12 +41,12 @@ The following arguments are supported:
 The following attributes are exported:
 
 * `auto_key_rotation_details` - The details of auto rotation schedule for the Key being create updated or imported.
-	* `last_rotation_message` - The last execution status message. 
+	* `last_rotation_message` - The last execution status message of auto key rotation. 
 	* `last_rotation_status` - The status of last execution of auto key rotation.
-	* `rotation_interval_in_days` - The interval of auto key rotation. For auto key rotation the interval should between 30 day and 365 days (1 year)
-	* `time_of_last_rotation` - A  property indicating Last rotation Date Example: `2023-04-04T00:00:00Z`.
-	* `time_of_next_rotation` - A property indicating Next estimated scheduled Time, as per the interval, expressed as date YYYY-MM-DD String. Example: `2023-04-04T00:00:00Z` .
-	* `time_of_schedule_start` - A property indicating  scheduled start date expressed as date YYYY-MM-DD String. Example: `2023-04-04T00:00:00Z` .
+	* `rotation_interval_in_days` - The interval of auto key rotation. For auto key rotation the interval should between 60 day and 365 days (1 year). Note: User must specify this parameter when creating a new schedule.
+	* `time_of_last_rotation` - A property indicating Last rotation Date. Example: `2023-04-04T00:00:00Z`.
+	* `time_of_next_rotation` - A property indicating Next estimated scheduled Time, as per the interval, expressed as date YYYY-MM-DD String. Example: `2023-04-04T00:00:00Z`. The time has no significance when scheduling an auto key rotation as this can be done anytime approximately the scheduled day, KMS ignores the time and replaces it with 00:00, for example 2023-04-04T15:14:13Z will be used as 2023-04-04T00:00:00Z. 
+	* `time_of_schedule_start` - A property indicating  scheduled start date expressed as date YYYY-MM-DD String. Example: `2023-04-04T00:00:00Z. The time has no significance when scheduling an auto key rotation as this can be done anytime approximately the scheduled day, KMS ignores the time and replaces it with 00:00, for example 2023-04-04T15:14:13Z will be used as 2023-04-04T00:00:00Z . Note : Today’s date will be used if not specified by customer.
 * `compartment_id` - The OCID of the compartment that contains this master encryption key.
 * `current_key_version` - The OCID of the key version used in cryptographic operations. During key rotation, the service might be in a transitional state where this or a newer key version are used intermittently. The `currentKeyVersion` property is updated when the service is guaranteed to use the new key version for all subsequent encryption operations. 
 * `defined_tags` - Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see [Resource Tags](https://docs.cloud.oracle.com/iaas/Content/General/Concepts/resourcetags.htm). Example: `{"Operations.CostCenter": "42"}` 

website/docs/d/kms_keys.html.markdown

@@ -57,12 +57,12 @@ The following attributes are exported:
 The following attributes are exported:
 
 * `auto_key_rotation_details` - The details of auto rotation schedule for the Key being create updated or imported.
-	* `last_rotation_message` - The last execution status message. 
+	* `last_rotation_message` - The last execution status message of auto key rotation. 
 	* `last_rotation_status` - The status of last execution of auto key rotation.
-	* `rotation_interval_in_days` - The interval of auto key rotation. For auto key rotation the interval should between 30 day and 365 days (1 year)
-	* `time_of_last_rotation` - A  property indicating Last rotation Date Example: `2023-04-04T00:00:00Z`.
-	* `time_of_next_rotation` - A property indicating Next estimated scheduled Time, as per the interval, expressed as date YYYY-MM-DD String. Example: `2023-04-04T00:00:00Z` .
-	* `time_of_schedule_start` - A property indicating  scheduled start date expressed as date YYYY-MM-DD String. Example: `2023-04-04T00:00:00Z` .
+	* `rotation_interval_in_days` - The interval of auto key rotation. For auto key rotation the interval should between 60 day and 365 days (1 year). Note: User must specify this parameter when creating a new schedule.
+	* `time_of_last_rotation` - A property indicating Last rotation Date. Example: `2023-04-04T00:00:00Z`.
+	* `time_of_next_rotation` - A property indicating Next estimated scheduled Time, as per the interval, expressed as date YYYY-MM-DD String. Example: `2023-04-04T00:00:00Z`. The time has no significance when scheduling an auto key rotation as this can be done anytime approximately the scheduled day, KMS ignores the time and replaces it with 00:00, for example 2023-04-04T15:14:13Z will be used as 2023-04-04T00:00:00Z. 
+	* `time_of_schedule_start` - A property indicating  scheduled start date expressed as date YYYY-MM-DD String. Example: `2023-04-04T00:00:00Z. The time has no significance when scheduling an auto key rotation as this can be done anytime approximately the scheduled day, KMS ignores the time and replaces it with 00:00, for example 2023-04-04T15:14:13Z will be used as 2023-04-04T00:00:00Z . Note : Today’s date will be used if not specified by customer.
 * `compartment_id` - The OCID of the compartment that contains this master encryption key.
 * `current_key_version` - The OCID of the key version used in cryptographic operations. During key rotation, the service might be in a transitional state where this or a newer key version are used intermittently. The `currentKeyVersion` property is updated when the service is guaranteed to use the new key version for all subsequent encryption operations. 
 * `defined_tags` - Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see [Resource Tags](https://docs.cloud.oracle.com/iaas/Content/General/Concepts/resourcetags.htm). Example: `{"Operations.CostCenter": "42"}` 

website/docs/d/kms_vault.html.markdown

@@ -52,6 +52,7 @@ The following attributes are exported:
 * `freeform_tags` - Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see [Resource Tags](https://docs.cloud.oracle.com/iaas/Content/General/Concepts/resourcetags.htm). Example: `{"Department": "Finance"}` 
 * `id` - The OCID of the vault.
 * `is_primary` - A Boolean value that indicates whether the Vault is primary Vault or replica Vault.
+* `is_vault_replicable` - A Boolean value that indicates whether the Vault has cross region replication capability. Always true for Virtual Private Vaults.
 * `management_endpoint` - The service endpoint to perform management operations against. Management operations include "Create," "Update," "List," "Get," and "Delete" operations. 
 * `replica_details` - Vault replica details 
 	* `replication_id` - ReplicationId associated with a vault operation 

website/docs/d/kms_vaults.html.markdown

@@ -58,6 +58,7 @@ The following attributes are exported:
 * `freeform_tags` - Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see [Resource Tags](https://docs.cloud.oracle.com/iaas/Content/General/Concepts/resourcetags.htm). Example: `{"Department": "Finance"}` 
 * `id` - The OCID of the vault.
 * `is_primary` - A Boolean value that indicates whether the Vault is primary Vault or replica Vault.
+* `is_vault_replicable` - A Boolean value that indicates whether the Vault has cross region replication capability. Always true for Virtual Private Vaults.
 * `management_endpoint` - The service endpoint to perform management operations against. Management operations include "Create," "Update," "List," "Get," and "Delete" operations. 
 * `replica_details` - Vault replica details 
 	* `replication_id` - ReplicationId associated with a vault operation 

website/docs/r/kms_key.html.markdown

@@ -62,12 +62,12 @@ resource "oci_kms_key" "test_key" {
 The following arguments are supported:
 
 * `auto_key_rotation_details` - (Optional) (Updatable) The details of auto rotation schedule for the Key being create updated or imported.
-	* `last_rotation_message` - (Optional) (Updatable) The last execution status message. 
+	* `last_rotation_message` - (Optional) (Updatable) The last execution status message of auto key rotation. 
 	* `last_rotation_status` - (Optional) (Updatable) The status of last execution of auto key rotation.
-	* `rotation_interval_in_days` - (Optional) (Updatable) The interval of auto key rotation. For auto key rotation the interval should between 30 day and 365 days (1 year)
-	* `time_of_last_rotation` - (Optional) (Updatable) A  property indicating Last rotation Date Example: `2023-04-04T00:00:00Z`.
-	* `time_of_next_rotation` - (Optional) (Updatable) A property indicating Next estimated scheduled Time, as per the interval, expressed as date YYYY-MM-DD String. Example: `2023-04-04T00:00:00Z` .
-	* `time_of_schedule_start` - (Optional) (Updatable) A property indicating  scheduled start date expressed as date YYYY-MM-DD String. Example: `2023-04-04T00:00:00Z` .
+	* `rotation_interval_in_days` - (Optional) (Updatable) The interval of auto key rotation. For auto key rotation the interval should between 60 day and 365 days (1 year). Note: User must specify this parameter when creating a new schedule.
+	* `time_of_last_rotation` - (Optional) (Updatable) A property indicating Last rotation Date. Example: `2023-04-04T00:00:00Z`.
+	* `time_of_next_rotation` - (Optional) (Updatable) A property indicating Next estimated scheduled Time, as per the interval, expressed as date YYYY-MM-DD String. Example: `2023-04-04T00:00:00Z`. The time has no significance when scheduling an auto key rotation as this can be done anytime approximately the scheduled day, KMS ignores the time and replaces it with 00:00, for example 2023-04-04T15:14:13Z will be used as 2023-04-04T00:00:00Z. 
+	* `time_of_schedule_start` - (Optional) (Updatable) A property indicating  scheduled start date expressed as date YYYY-MM-DD String. Example: `2023-04-04T00:00:00Z. The time has no significance when scheduling an auto key rotation as this can be done anytime approximately the scheduled day, KMS ignores the time and replaces it with 00:00, for example 2023-04-04T15:14:13Z will be used as 2023-04-04T00:00:00Z . Note : Today’s date will be used if not specified by customer.
 * `compartment_id` - (Required) (Updatable) The OCID of the compartment where you want to create the master encryption key.
 * `defined_tags` - (Optional) (Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see [Resource Tags](https://docs.cloud.oracle.com/iaas/Content/General/Concepts/resourcetags.htm). Example: `{"Operations.CostCenter": "42"}` 
 * `desired_state` - (Optional) (Updatable) Desired state of the key. Possible values : `ENABLED` or `DISABLED`
@@ -106,12 +106,12 @@ Any change to a property that does not support update will force the destruction
 The following attributes are exported:
 
 * `auto_key_rotation_details` - The details of auto rotation schedule for the Key being create updated or imported.
-	* `last_rotation_message` - The last execution status message. 
+	* `last_rotation_message` - The last execution status message of auto key rotation. 
 	* `last_rotation_status` - The status of last execution of auto key rotation.
-	* `rotation_interval_in_days` - The interval of auto key rotation. For auto key rotation the interval should between 30 day and 365 days (1 year)
-	* `time_of_last_rotation` - A  property indicating Last rotation Date Example: `2023-04-04T00:00:00Z`.
-	* `time_of_next_rotation` - A property indicating Next estimated scheduled Time, as per the interval, expressed as date YYYY-MM-DD String. Example: `2023-04-04T00:00:00Z` .
-	* `time_of_schedule_start` - A property indicating  scheduled start date expressed as date YYYY-MM-DD String. Example: `2023-04-04T00:00:00Z` .
+	* `rotation_interval_in_days` - The interval of auto key rotation. For auto key rotation the interval should between 60 day and 365 days (1 year). Note: User must specify this parameter when creating a new schedule.
+	* `time_of_last_rotation` - A property indicating Last rotation Date. Example: `2023-04-04T00:00:00Z`.
+	* `time_of_next_rotation` - A property indicating Next estimated scheduled Time, as per the interval, expressed as date YYYY-MM-DD String. Example: `2023-04-04T00:00:00Z`. The time has no significance when scheduling an auto key rotation as this can be done anytime approximately the scheduled day, KMS ignores the time and replaces it with 00:00, for example 2023-04-04T15:14:13Z will be used as 2023-04-04T00:00:00Z. 
+	* `time_of_schedule_start` - A property indicating  scheduled start date expressed as date YYYY-MM-DD String. Example: `2023-04-04T00:00:00Z. The time has no significance when scheduling an auto key rotation as this can be done anytime approximately the scheduled day, KMS ignores the time and replaces it with 00:00, for example 2023-04-04T15:14:13Z will be used as 2023-04-04T00:00:00Z . Note : Today’s date will be used if not specified by customer.
 * `compartment_id` - The OCID of the compartment that contains this master encryption key.
 * `current_key_version` - The OCID of the key version used in cryptographic operations. During key rotation, the service might be in a transitional state where this or a newer key version are used intermittently. The `currentKeyVersion` property is updated when the service is guaranteed to use the new key version for all subsequent encryption operations. 
 * `defined_tags` - Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see [Resource Tags](https://docs.cloud.oracle.com/iaas/Content/General/Concepts/resourcetags.htm). Example: `{"Operations.CostCenter": "42"}` 

website/docs/r/kms_vault.html.markdown

@@ -96,6 +96,7 @@ The following attributes are exported:
 * `freeform_tags` - Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see [Resource Tags](https://docs.cloud.oracle.com/iaas/Content/General/Concepts/resourcetags.htm). Example: `{"Department": "Finance"}` 
 * `id` - The OCID of the vault.
 * `is_primary` - A Boolean value that indicates whether the Vault is primary Vault or replica Vault.
+* `is_vault_replicable` - A Boolean value that indicates whether the Vault has cross region replication capability. Always true for Virtual Private Vaults.
 * `management_endpoint` - The service endpoint to perform management operations against. Management operations include "Create," "Update," "List," "Get," and "Delete" operations. 
 * `replica_details` - Vault replica details 
 	* `replication_id` - ReplicationId associated with a vault operation