Open jurgen-weber-deltatre opened 1 year ago
Voting for Prioritization
Volunteering to Work on This Issue
I think we are suffering from this bug, but our Redshift cluster was not restored at all. It's been created under Terraform control from the start, but changing the master_password parameter similarly does nothing.
Also faced this problem, this bug destroys the whole process of deploying new infrastructure
Terraform v1.5.5 on linux_amd64
Hi @jurgen-weber-deltatre do you find workaround for this problem ?
Also faced this issue recently and it blocks big peace of my work. Is there any workaround? Also, if there is something I can do to help to resolve this issue please ping me.
Terraform Core Version
1.3.3
AWS Provider Version
4.37.0
Affected Resource(s)
Our aws_redshift_cluster was originally migration from a snapshot; so snapshot_identifier was set. After the restoration has been completed we then removed this setting so it does not restore on every plan/apply.
Now at the same time, the master_username and master_password were set, but as the documentation says it is ignored or not required when you are restoring.
Now I wish to rotate the password, this does nothing. I know the password has changed because other resources related to it are changing/updating but on a plan no change happens to the aws_redshift_cluster resource.
If I change the username, the AWS API seems to want to recreate the whole thing.. Which of course I Don't want to recreate my redshift cluster. I just want to change the master password.
Expected Behavior
An 'update in place' action to happen on the aws_redshift_cluster resource.
Actual Behavior
Nothing, absolutely nothing happens even thought hte master_password has changed.
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files