[Bug]: Validation error on updating enhanced_vpc_routing for aws_redshiftserverless_workgroup

[meetvasu15]

Terraform Core Version

1.1.5

AWS Provider Version

4.31.0

Affected Resource(s)

• aws_redshiftserverless_workgroup

Expected Behavior

enhanced_vpc_routing is updated to true.

Actual Behavior

Terraform recognizes correctly the flag for enhanced_vpc_routing needs to be changed from false to true however during apply fails with a validation exception.

Relevant Error/Panic Output Snippet

aws_redshiftserverless_workgroup.xxxxx: Modifying... [id=xxxxx]
╷
│ Error: error updating Redshift Serverless Workgroup (xxxxx): ValidationException: Can't update multiple configurations at the same time for workgroup xxxxx.
│
│   with aws_redshiftserverless_workgroup.xxxxx,
│   on redshift.tf line 96, in resource "aws_redshiftserverless_workgroup" "xxxxx":
│   96: resource "aws_redshiftserverless_workgroup" "xxxxx" {
│

Terraform Configuration Files

resource "aws_redshiftserverless_workgroup" "xxxxx" {
  namespace_name       = aws_redshiftserverless_namespace.xxxxx-namespace.id
  workgroup_name       = "xxxxx"
  base_capacity        = 32
  publicly_accessible  = false
  enhanced_vpc_routing = true
  subnet_ids           = data.terraform_remote_state.vpc.outputs.module_vpc_private_subnets
}

Steps to Reproduce

1. Create a redshift serveless workgroup with enhanced_vpc_routing set to false (default).
2. Update redshift serveless workgroup and set enhanced_vpc_routing to true.

Debug Output

No response

Panic Output

No response

Important Factoids

None

References

No response

Would you like to implement a fix?

No

[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.

[meetvasu15]

On further debugging it seems like AWS CLI doesnt like multiple config params being updated in serverless updateworkgroup call which I think is a bug for AWS to resolve, opened 7505 for that. However when updating just the enhanced_vpc_routing there is no need to resend the config parameters when there is no change in them.

[meetvasu15]

Opened 28255 therefore closing this issue

[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.