-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
resource/aws_redshift_cluster: Use availability status instead of fine-grained status when waiting for operations #23638
Comments
…r cluster state changes (hashicorp#23638). Acceptance test output: % make testacc TESTS=TestAccRedshiftCluster_ PKG=redshift ACCTEST_PARALLELISM=3 ==> Checking that code complies with gofmt requirements... TF_ACC=1 go test ./internal/service/redshift/... -v -count 1 -parallel 3 -run='TestAccRedshiftCluster_' -timeout 180m === RUN TestAccRedshiftCluster_basic === PAUSE TestAccRedshiftCluster_basic === RUN TestAccRedshiftCluster_disappears === PAUSE TestAccRedshiftCluster_disappears === RUN TestAccRedshiftCluster_withFinalSnapshot === PAUSE TestAccRedshiftCluster_withFinalSnapshot === RUN TestAccRedshiftCluster_kmsKey === PAUSE TestAccRedshiftCluster_kmsKey === RUN TestAccRedshiftCluster_enhancedVPCRoutingEnabled === PAUSE TestAccRedshiftCluster_enhancedVPCRoutingEnabled === RUN TestAccRedshiftCluster_loggingEnabled === PAUSE TestAccRedshiftCluster_loggingEnabled === RUN TestAccRedshiftCluster_snapshotCopy === PAUSE TestAccRedshiftCluster_snapshotCopy === RUN TestAccRedshiftCluster_iamRoles === PAUSE TestAccRedshiftCluster_iamRoles === RUN TestAccRedshiftCluster_publiclyAccessible === PAUSE TestAccRedshiftCluster_publiclyAccessible === RUN TestAccRedshiftCluster_updateNodeCount === PAUSE TestAccRedshiftCluster_updateNodeCount === RUN TestAccRedshiftCluster_updateNodeType === PAUSE TestAccRedshiftCluster_updateNodeType === RUN TestAccRedshiftCluster_tags === PAUSE TestAccRedshiftCluster_tags === RUN TestAccRedshiftCluster_forceNewUsername === PAUSE TestAccRedshiftCluster_forceNewUsername === RUN TestAccRedshiftCluster_changeAvailabilityZone === PAUSE TestAccRedshiftCluster_changeAvailabilityZone === RUN TestAccRedshiftCluster_changeAvailabilityZoneAndSetAvailabilityZoneRelocation === PAUSE TestAccRedshiftCluster_changeAvailabilityZoneAndSetAvailabilityZoneRelocation === RUN TestAccRedshiftCluster_changeAvailabilityZone_availabilityZoneRelocationNotSet === PAUSE TestAccRedshiftCluster_changeAvailabilityZone_availabilityZoneRelocationNotSet === RUN TestAccRedshiftCluster_changeEncryption1 === PAUSE TestAccRedshiftCluster_changeEncryption1 === RUN TestAccRedshiftCluster_changeEncryption2 === PAUSE TestAccRedshiftCluster_changeEncryption2 === RUN TestAccRedshiftCluster_availabilityZoneRelocation === PAUSE TestAccRedshiftCluster_availabilityZoneRelocation === RUN TestAccRedshiftCluster_availabilityZoneRelocation_publiclyAccessible === PAUSE TestAccRedshiftCluster_availabilityZoneRelocation_publiclyAccessible === CONT TestAccRedshiftCluster_basic === CONT TestAccRedshiftCluster_updateNodeType === CONT TestAccRedshiftCluster_changeAvailabilityZone_availabilityZoneRelocationNotSet --- PASS: TestAccRedshiftCluster_basic (222.68s) === CONT TestAccRedshiftCluster_availabilityZoneRelocation --- PASS: TestAccRedshiftCluster_changeAvailabilityZone_availabilityZoneRelocationNotSet (390.44s) === CONT TestAccRedshiftCluster_changeEncryption2 --- PASS: TestAccRedshiftCluster_availabilityZoneRelocation (456.19s) === CONT TestAccRedshiftCluster_changeEncryption1 --- PASS: TestAccRedshiftCluster_updateNodeType (1428.13s) === CONT TestAccRedshiftCluster_availabilityZoneRelocation_publiclyAccessible === CONT TestAccRedshiftCluster_changeAvailabilityZone --- PASS: TestAccRedshiftCluster_availabilityZoneRelocation_publiclyAccessible (2.04s) --- PASS: TestAccRedshiftCluster_changeAvailabilityZone (518.74s) === CONT TestAccRedshiftCluster_changeAvailabilityZoneAndSetAvailabilityZoneRelocation --- PASS: TestAccRedshiftCluster_changeEncryption2 (1651.28s) === CONT TestAccRedshiftCluster_loggingEnabled --- PASS: TestAccRedshiftCluster_changeEncryption1 (1640.72s) === CONT TestAccRedshiftCluster_iamRoles --- PASS: TestAccRedshiftCluster_loggingEnabled (336.16s) === CONT TestAccRedshiftCluster_snapshotCopy --- PASS: TestAccRedshiftCluster_changeAvailabilityZoneAndSetAvailabilityZoneRelocation (682.67s) === CONT TestAccRedshiftCluster_forceNewUsername --- PASS: TestAccRedshiftCluster_snapshotCopy (288.47s) === CONT TestAccRedshiftCluster_publiclyAccessible --- PASS: TestAccRedshiftCluster_iamRoles (402.34s) === CONT TestAccRedshiftCluster_updateNodeCount --- PASS: TestAccRedshiftCluster_publiclyAccessible (304.97s) === CONT TestAccRedshiftCluster_tags --- PASS: TestAccRedshiftCluster_forceNewUsername (503.93s) === CONT TestAccRedshiftCluster_kmsKey --- PASS: TestAccRedshiftCluster_tags (255.92s) === CONT TestAccRedshiftCluster_enhancedVPCRoutingEnabled --- PASS: TestAccRedshiftCluster_kmsKey (420.64s) === CONT TestAccRedshiftCluster_withFinalSnapshot --- PASS: TestAccRedshiftCluster_enhancedVPCRoutingEnabled (649.53s) === CONT TestAccRedshiftCluster_disappears --- PASS: TestAccRedshiftCluster_withFinalSnapshot (496.08s) --- PASS: TestAccRedshiftCluster_disappears (247.65s) --- PASS: TestAccRedshiftCluster_updateNodeCount (1669.39s) PASS ok github.com/hashicorp/terraform-provider-aws/internal/service/redshift 4394.922s
This functionality has been released in v4.9.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
In the AWS API, the Redshift Cluster has two status fields:
ClusterAvailabilityStatus
can have the valuesAvailable
,Unavailable
,Maintenance
,Modifying
, orFailed
ClusterStatus
has more fine-grained status conditions, including at least one,recovering
, which is not documentedThe AWS Console displays both, with the availability status being more prominent.
ClusterAvailabilityStatus
should be enough when waiting for operations on the clusterAffected Resource
The text was updated successfully, but these errors were encountered: