Wait for DC archival location operations to finish (#203)

The data_center_archival_location_amazon_s3 resource will now monitor
and wait for asynchronous CDM operations to finish.

Author: johan3141592

docs/guides/changelog.md

@@ -4,6 +4,14 @@ page_title: "Changelog"
 
 # Changelog
 
+## v0.10.0-beta.5
+* The data_center_archival_location_amazon_s3 resource will now monitor and wait for the asynchronous CDM operations to
+  finish.
+
+## v0.10.0-beta.4
+* Fix a regression in the cloud native archival location resources. An extra level of structure in the RSC response
+  caused resource refreshes to fail.
+
 ## v0.10.0-beta.3
 * Add support for creating data center AWS accounts. [[docs](../resources/data_center_aws_account)]
 * Add support for creating data center Azure subscriptions. [[docs](../resources/data_center_azure_subscription)]

docs/resources/data_center_archival_location_amazon_s3.md

@@ -5,12 +5,6 @@ subcategory: ""
 description: |-
   The polaris_data_center_archival_location_amazon_s3 resource create a data
   center archival location with the Amazon S3 storage type.
-  ~> The actual creation/deletion of a data center archival location runs
-     asynchronously on a CDM cluster outside the control of Terraform. This means
-     the operation can fail after Terraform has succeeded. A failure in the
-     asynchronous task which creates an archival location will result in the
-     archival location getting removed from RSC or its sync_status never
-     reaching the SYNCED state.
   ~> Before configuring the immutability settings, see
      KB article https://support.rubrik.com/s/article/000005468 or the Rubrik
      User Guide documentation to determine the proper immutability lock period.
@@ -23,13 +17,6 @@ description: |-
 The `polaris_data_center_archival_location_amazon_s3` resource create a data
 center archival location with the Amazon S3 storage type.
 
-~> The actual creation/deletion of a data center archival location runs
-   asynchronously on a CDM cluster outside the control of Terraform. This means
-   the operation can fail after Terraform has succeeded. A failure in the
-   asynchronous task which creates an archival location will result in the
-   archival location getting removed from RSC or its `sync_status` never
-   reaching the `SYNCED` state.
-
 ~> Before configuring the immutability settings, see
    [KB article](https://support.rubrik.com/s/article/000005468) or the Rubrik
    User Guide documentation to determine the proper immutability lock period.

go.mod

@@ -8,7 +8,7 @@ require (
 	github.com/hashicorp/go-cty v1.4.1-0.20200414143053-d3edf31b6320
 	github.com/hashicorp/terraform-plugin-docs v0.16.0
 	github.com/hashicorp/terraform-plugin-sdk/v2 v2.34.0
-	github.com/rubrikinc/rubrik-polaris-sdk-for-go v0.11.0-beta.5
+	github.com/rubrikinc/rubrik-polaris-sdk-for-go v0.11.0-beta.6
 )
 
 require (

go.sum

@@ -270,8 +270,8 @@ github.com/posener/complete v1.2.3/go.mod h1:WZIdtGGp+qx0sLrYKtIRAruyNpv6hFCicSg
 github.com/prometheus/client_model v0.0.0-20190812154241-14fe0d1b01d4/go.mod h1:xMI15A0UPsDsEKsMN9yxemIoYk6Tm2C1GtYGdfGttqA=
 github.com/rogpeppe/go-internal v1.6.1 h1:/FiVV8dS/e+YqF2JvO3yXRFbBLTIuSDkuC7aBOAvL+k=
 github.com/rogpeppe/go-internal v1.6.1/go.mod h1:xXDCJY+GAPziupqXw64V24skbSoqbTEfhy4qGm1nDQc=
-github.com/rubrikinc/rubrik-polaris-sdk-for-go v0.11.0-beta.5 h1:MlF2JQh/z4QfQ1mcsiQrQwWBEvPP0PC6KCMtRPHSgbA=
-github.com/rubrikinc/rubrik-polaris-sdk-for-go v0.11.0-beta.5/go.mod h1:ryJGDKlbaCvozY3Wvt+TPSN2OZRChQedHUNsnVfCbXE=
+github.com/rubrikinc/rubrik-polaris-sdk-for-go v0.11.0-beta.6 h1:7tIuXO7wf/zLBmYtd3HXevp733UeHRY5VzrLSzgA57g=
+github.com/rubrikinc/rubrik-polaris-sdk-for-go v0.11.0-beta.6/go.mod h1:ryJGDKlbaCvozY3Wvt+TPSN2OZRChQedHUNsnVfCbXE=
 github.com/russross/blackfriday v1.6.0 h1:KqfZb0pUVN2lYqZUYRddxF4OR8ZMURnJIG5Y3VRLtww=
 github.com/russross/blackfriday v1.6.0/go.mod h1:ti0ldHuxg49ri4ksnFxlkCfN+hvslNlmVHqNRXXJNAY=
 github.com/sergi/go-diff v1.3.2-0.20230802210424-5b0b94c5c0d3 h1:n661drycOFuPLCN3Uc8sB6B/s6Z4t2xvBgU1htSHuq8=

internal/provider/resource_data_center_archival_location_amazon_s3.go

@@ -39,13 +39,6 @@ const resourceDataCenterArchivalLocationAmazonS3Description = `
 The ´polaris_data_center_archival_location_amazon_s3´ resource create a data
 center archival location with the Amazon S3 storage type.
 
-~> The actual creation/deletion of a data center archival location runs
-   asynchronously on a CDM cluster outside the control of Terraform. This means
-   the operation can fail after Terraform has succeeded. A failure in the
-   asynchronous task which creates an archival location will result in the
-   archival location getting removed from RSC or its ´sync_status´ never
-   reaching the ´SYNCED´ state.
-
 ~> Before configuring the immutability settings, see
    [KB article](https://support.rubrik.com/s/article/000005468) or the Rubrik
    User Guide documentation to determine the proper immutability lock period.

templates/guides/changelog.md.tmpl

@@ -4,6 +4,14 @@ page_title: "Changelog"
 
 # Changelog
 
+## v0.10.0-beta.5
+* The data_center_archival_location_amazon_s3 resource will now monitor and wait for the asynchronous CDM operations to
+  finish.
+
+## v0.10.0-beta.4
+* Fix a regression in the cloud native archival location resources. An extra level of structure in the RSC response
+  caused resource refreshes to fail.
+
 ## v0.10.0-beta.3
 * Add support for creating data center AWS accounts. [[docs](../resources/data_center_aws_account)]
 * Add support for creating data center Azure subscriptions. [[docs](../resources/data_center_azure_subscription)]