-
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
[Bug] [aws_emr_instance_fleet] allocation_strategy does not detect correctly #34151
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
It looks like when the resource is read into Terraform, the allocation strategy is hardcoded to The commented line above the linked one would probably fix the problem, assuming the value coming back from the AWS API is lowercase. As a note, this seems to be both a bug and outdated code. In the past, the only value supported is
But the JSON format/schema provides multiple allowed values:
|
It looks like the change in the attribute value not only applies to The ListInstanceFleets API indicates that the lower-case names should be returned, as with the
|
This is an issue when trying to create an
|
I was using an older version of the provider in my test setup; Creating a cluster works as expected. |
This functionality has been released in v5.36.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! |
Confirmed this issue has been fixed, thanks! ☀️ |
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.6.2
AWS Provider Version
5.23.1
Affected Resource(s)
Expected Behavior
I have Amazon EMR Instance Fleet provisioned by Terraform. Inside task node
allocation_strategy
is using "price-capacity-optimized". Terraform created the whole EMR cluster correctly.However, I run
terraform apply
second time, Terraform cannot detect current Amazon EMR Instance Fleet'sallocation_strategy
correctly.Actual Behavior
Terraform detects
allocation_strategy
wrong. It thinks it is "capacity-optimized" which actually is "price-capacity-optimized".Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
terraform apply
terraform plan
, you will see for aws_emr_instance_fleet, itsallocation_strategy
is supposed to be detected as "price-capacity-optimized", instead Terraform detects it as "capacity-optimized".Debug Output
https://gist.github.com/hongbo-miao/080208ee300d9561e37f48450dd0bfd1
Workaround Solution
Add
to ignore detecting "allocation_strategy".
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: