[Bug]: r/aws_redshiftserverless_namespace: unable to update multiple attributes at the same time

[marcinbelczewski]

Terraform Core Version

1.9.5

AWS Provider Version

5.66.0

Affected Resource(s)

• aws_redshiftserverless_namespace

Expected Behavior

Resource updated succesfully

Actual Behavior

AWS API error:

Plan: 0 to add, 1 to change, 0 to destroy.
aws_redshiftserverless_namespace.test: Modifying... [id=test]
╷
│ Error: updating Redshift Serverless Namespace (test): operation error Redshift Serverless: UpdateNamespace, https response error StatusCode: 400, RequestID: 2cff8457-8535-442f-b7b6-c93113c69336, ValidationException: Amazon Redshift Serverless can't update multiple configurations at the same time for namespace test.
│
│   with aws_redshiftserverless_namespace.test,
│   on main.tf line 19, in resource "aws_redshiftserverless_namespace" "test":
│   19: resource "aws_redshiftserverless_namespace" "test" {
│
╵

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

resource "aws_redshiftserverless_namespace" "test" {
namespace_name = "test"
admin_username = "test"
admin_user_password = "Password1234!"
log_exports = ["userlog"]
}

Steps to Reproduce

1. Apply the following configuration first:

resource "aws_redshiftserverless_namespace" "test" {
  namespace_name = "test"
}

2. Update several attributes and try applying configuration:

resource "aws_redshiftserverless_namespace" "test" {
  namespace_name = "test"
  admin_username = "test"
  admin_user_password = "Password1234!"
  log_exports = ["userlog"]
}

Debug Output

No response

Panic Output

No response

Important Factoids

The cause is the limitation in the Redshift Serverless UpdateNamespace API where multiple attributes cannot be updated at the same time. This is not unlike Workgroup API which already supports sequence of updates in the provider.

References

No response

Would you like to implement a fix?

Yes

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• 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.