-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
[Bug]: When updating attributes like base capacity, publicly_accessible or enhanced vpc routing in aws_redshiftserverless_workgroup update to config params is also triggered #28255
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Has anyone looked into this yet? Seems like this is still an ongoing issue. After deploying a redshift serverless instance, changing the base_capacity is not possible due to this error. Is there any workaround at the moment? this is a bit frustrating since it means we can easily make changes once we've deployed this to production. Deleting and recreating isn't an ideal solution... |
Similar: #27973. |
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. |
Terraform Core Version
1.1.5
AWS Provider Version
4.31.0
Affected Resource(s)
Expected Behavior
Update to attributes such as base capacity, enhanced_vpc_routing and publicly accessible should not trigger update on config parameters.
Actual Behavior
Update to attributes such as base capacity, enhanced_vpc_routing and publicly accessible triggers update to config parameters causing a validation exception.
Relevant Error/Panic Output Snippet
Terraform Configuration Files
Steps to Reproduce
Debug Output
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: