-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Unexpected changes with aws_emr_cluster when using instance_group list #7278
Comments
I have also tried specifying 3 separate
I even tried re-ordering the above without luck -- the |
The fix for this (#7324) has been merged and will release with version 1.57.0 of the Terraform AWS provider, likely later today. |
👍 thank you!. As a note I was able to work around this problem, it seems, by removing the |
This has been released in version 1.57.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Community Note
Terraform Version
Affected Resource(s)
Terraform Configuration Files
And variables:
Debug Output
Expected Behavior
No changes.
Actual Behavior
Changes:
Steps to Reproduce
terraform plan
orapply
with anaws_emr_cluster
that usesinstance_group
Important Factoids
Even after an
apply
, subsequentplan
s show more of the same changes.References
#6498 may be relevant, as this change was not happening with 1.55.0 and started only after 1.56.0 (and template 2.0.0). I believe
instance_group
is getting reordered as part of the plan by list/set conversions.The text was updated successfully, but these errors were encountered: