-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
fix: add validation to passwords field of elasticache replication group #24274
fix: add validation to passwords field of elasticache replication group #24274
Conversation
Signed-off-by: Dustin Scott <[email protected]>
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.
Welcome @scottd018 👋
It looks like this is your first Pull Request submission to the Terraform AWS Provider! If you haven’t already done so please make sure you have checked out our CONTRIBUTING guide and FAQ to make sure your contribution is adhering to best practice and has all the necessary elements in place for a successful approval.
Also take a look at our FAQ which details how we prioritize Pull Requests for inclusion.
Thanks again, and welcome to the community! 😃
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 TESTS=TestAccElastiCacheUser_ PKG=elasticache ACCTEST_PARALLELISM=2
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/elasticache/... -v -count 1 -parallel 2 -run='TestAccElastiCacheUser_' -timeout 180m
=== RUN TestAccElastiCacheUser_basic
=== PAUSE TestAccElastiCacheUser_basic
=== RUN TestAccElastiCacheUser_update
=== PAUSE TestAccElastiCacheUser_update
=== RUN TestAccElastiCacheUser_tags
=== PAUSE TestAccElastiCacheUser_tags
=== RUN TestAccElastiCacheUser_disappears
=== PAUSE TestAccElastiCacheUser_disappears
=== CONT TestAccElastiCacheUser_basic
=== CONT TestAccElastiCacheUser_tags
--- PASS: TestAccElastiCacheUser_basic (78.56s)
=== CONT TestAccElastiCacheUser_disappears
--- PASS: TestAccElastiCacheUser_tags (84.54s)
=== CONT TestAccElastiCacheUser_update
--- PASS: TestAccElastiCacheUser_disappears (71.48s)
--- PASS: TestAccElastiCacheUser_update (124.47s)
PASS
ok github.com/hashicorp/terraform-provider-aws/internal/service/elasticache 216.950s
@scottd018 Thanks for the contribution 🎉 👏. |
Thanks @ewbankkit ! |
This functionality has been released in v4.11.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. |
This PR adds in the validation logic using existing validation with the SDK to validate that a user password for an elasticache cluster is within a specific range. Without this, a module may fail after initial validation which is especially problematic for long running Terraform scripts.
Signed-off-by: Dustin Scott [email protected]
Community Note
Closes #24273
Output from acceptance testing: