-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
aws_msk_cluster not using the latest revision of aws_msk_configuration #17484
Comments
We are observing the same issue |
For reference, adding a
At least it makes the bug explicit. The only workaround I know of so far is to apply the terraform configuration twice -- once to create the new configuration revision, and the second to get the cluster to use it. |
Although I am seeing the same behaviour as described in the issue. I would like to present a solution that actually works on a single apply of terraform scripts.
Using data source, terraform correctly updates cluster with the latest revision of cluster configuration. Hope that will help some of you! :) |
I can confirm that the @marcincuber workaround do work! Thanks for that little gem! |
I think the workaround depends on changes to dependency handling introduced in Terraform 0.13.0 (I know, I know). It doesn't work with 0.12. |
This functionality has been released in v4.6.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! |
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. |
Community Note
Terraform CLI and Terraform AWS Provider Version
Affected Resource(s)
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
When updating a value from the
aws_msk_configuration
resource, theaws_msk_cluster
pointing to this configuration should pick the latest revision of the configurationActual Behavior
The
aws_msk_configuration
resource correctly gets updated with the new confioguration values and a new revision of the configuration is created, however MSK is still using revision N-1 and a second terraform plan application is needed to have MSK point to the latest revisionSteps to Reproduce
terraform init
terraform plan
terraform apply
Important Factoids
It is worth noting than the MSK configuration and MSK cluster resources are defined in the same terraform module.
References
The text was updated successfully, but these errors were encountered: