Namespace can be updated to switch from explicit admin user password provided in the configuration, to managing the password via Secrets Manager. Such a change is supported by the API
Actual Behavior
Error when applying configuration switching from user provider admin password to managed one:
aws_redshiftserverless_namespace.test: Modifying... [id=test]
╷
│ Error: updating Redshift Serverless Namespace (test): operation error Redshift Serverless: UpdateNamespace, https response error StatusCode: 400, RequestID: 13774622-d1e9-41ca-bcd0-17cb86931b1b, ValidationException: 1 validation error detected: Value at 'adminUserPassword' failed to satisfy constraint: Member must have length greater than or equal to 8
│
│ with aws_redshiftserverless_namespace.test,
│ on main.tf line 19, in resource "aws_redshiftserverless_namespace" "test":
│ 19: resource "aws_redshiftserverless_namespace" "test" {
│
╵
Provider does not recognize a switch from unmanaged to managed password and still insists on validating admin password from the configuration (there is non on the update)
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
Volunteering to Work on This Issue
If you are interested in working on this issue, please leave a comment.
If this would be your first contribution, please review the contribution guide.
Terraform Core Version
1.9.5
AWS Provider Version
5.66.0
Affected Resource(s)
Expected Behavior
Namespace can be updated to switch from explicit admin user password provided in the configuration, to managing the password via Secrets Manager. Such a change is supported by the API
Actual Behavior
Error when applying configuration switching from user provider admin password to managed one:
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
Another variant to reproduce the same problem:
Debug Output
No response
Panic Output
No response
Important Factoids
Provider does not recognize a switch from unmanaged to managed password and still insists on validating admin password from the configuration (there is non on the update)
References
No response
Would you like to implement a fix?
Yes