Closed matschundbrei closed 1 year ago
Voting for Prioritization
Volunteering to Work on This Issue
The two new additional configuration keys are not showing in the CLI documentation either.
edit: redacted internal ids
possible solution is to change the params to set instead of list type and remove validation for key. ill take a look if someone wont before i do.
Error: error creating Redshift Serverless Workgroup : ValidationException: The parameter key auto_mv isn't supported. Supported values: [[max_query_execution_time, search_path, datestyle, query_group, enable_user_activity_logging]]
so one thing before the ordering issue, some of the options. arent valid even if i remove the provider side validation
@DrFaust92 I think ordering them right wont resolve it for now, seems like there is an underlying issue with updating the config_parameter with the UpdateWorkgroup API. The work around suggested is to basically recreate the workgroup if there are changes to config param. aws/aws-cli #7507
FWIW, changes to anything other than config_parameter block of the workgroup must not trigger a UpdateWorkgroup API call with config_parameter value in them for that see hashicorp/terrafrom#28255
Hey guys, is there any news related to this? Thanks
The additional parameters need to be enabled for the drift to disappear. The api documentation already includes them.
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.
Terraform Core Version
1.3.5
AWS Provider Version
4.40.0
Affected Resource(s)
Expected Behavior
Apply config parameters consistently
Actual Behavior
Two new out of order
config_parameter
appear, that I cannot control from terraform (see Errors), changes persist between runs and cannot be applied (see Errors)Relevant Error/Panic Output Snippet
Terraform Configuration Files
I left out IAM (aws_iam_role.redshift.arn) and VPC (data.aws_subnets.private.ids) config to keep up clarity, ping me if you need an example.
Steps to Reproduce
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
No