-
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
r/aws_redshift_cluster: support managed master passwords #34182
Conversation
Community NoteVoting for Prioritization
For Submitters
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚀.
% make testacc TESTARGS='-run=TestAccRedshiftCluster_manageMasterPassword\|TestAccRedshiftCluster_basic' PKG=redshift ACCTEST_PARALLELISM=2
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/redshift/... -v -count 1 -parallel 2 -run=TestAccRedshiftCluster_manageMasterPassword\|TestAccRedshiftCluster_basic -timeout 360m
=== RUN TestAccRedshiftCluster_basic
=== PAUSE TestAccRedshiftCluster_basic
=== RUN TestAccRedshiftCluster_manageMasterPassword
=== PAUSE TestAccRedshiftCluster_manageMasterPassword
=== CONT TestAccRedshiftCluster_basic
=== CONT TestAccRedshiftCluster_manageMasterPassword
--- PASS: TestAccRedshiftCluster_manageMasterPassword (239.27s)
--- PASS: TestAccRedshiftCluster_basic (253.89s)
PASS
ok github.com/hashicorp/terraform-provider-aws/internal/service/redshift 260.471s
This change adds the manage_master_password and master_password_secret_kms_key_id arguments allowing the configuration of AWS managed credentials via SecretsManager. The manage_master_password argument conflicts with the master_password argument, and at least one must be set when creating a new cluster not restored from a snapshot. The master_password_secret_arn attribute was added to track the ARN of the SecretsManager secret which stores cluster credentials.
84767cd
to
fc2fa19
Compare
This functionality has been released in v5.24.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 pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Description
This change adds the
manage_master_password
andmaster_password_secret_kms_key_id
arguments allowing the configuration of AWS managed credentials via SecretsManager. Themanage_master_password
argument conflicts with themaster_password
argument, and at least one must be set when creating a new cluster not restored from a snapshot. Themaster_password_secret_arn
attribute was added to track the ARN of the SecretsManager secret which stores cluster credentials.Relations
Closes #34169
References
Output from Acceptance Testing