[Bug]: Updating aws_redshiftserverless_workgroup base and max capacities failures

[marcinbelczewski]

Terraform Core Version

1.7.4

AWS Provider Version

5.38.0

Affected Resource(s)

aws_redshiftserverless_workgroup

Expected Behavior

Updating base_capacity and max_capacity should succeed no matter what current and new values are as long those are within acceptable limits.

Actual Behavior

Since Amazon Redshift Serverless API only allows for updating Workgroups one attribute at a time, the ordering of updates of base_capacity and max_capacity on aws_redshiftserverless_workgroup matters. Currently, provider updates attributes in alphabetical order so base_capacity is update first and then max_capacity.
So, if for example current base_capacity is 128 and max_capacity is 256, and new update is attempted for base_capacity to 512 and max_capacity to 1024, the first update to base_capacity will fail as it's larger value than current max_capacity of 256. In this case, max_capacity should be updated first to 1024 and only after base_capacity to 512.

When lowering the values for base_capacity and max_capacity, the reverse order is often required to first lower base_capacity and only after lower max_capacity.

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

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

resource "aws_redshiftserverless_workgroup" "this" {
  namespace_name = aws_redshiftserverless_namespace.this.namespace_name
  workgroup_name = "test"
  base_capacity  = 128
  max_capacity   = 256
}

Steps to Reproduce

Update the base_capacity to 512 and max_capacity to 1024 and apply. It will fail.

Debug Output

No response

Panic Output

No response

Important Factoids

No response

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.

[github-actions]

This functionality has been released in v5.39.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!

[github-actions]

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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.