provider/aws: Fix EMR Bootstrap Action Ordering #13580
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
aws_emr_cluster
has abootstrap_actions
parameter, which itself has anargs
parameter.args
is stored as aTypeSet
, which does not preserve ordering of it's items. See #10691.In this PR we change the
args
fromTypeSet
toTypeList
.This is considered a Breaking Change.. kind of (BC)
Users who upgrade to this version will experience a diff on their next
plan
run, however, this is deemed necessary because of the lack of ordering that's currently in place. Essentially, users have specified the order, but Terraform is not honoring that, and the API may have a different order. Changing this is required, and it can't be migrated because the change will need to happen on the API side as well.TestAccAWSEMRCluster_bootstrap_ordering
, a failing test for EMR Bootstrap Actions, demonstrating the problemFixes #10691
The failing test, before the fix:
After the fix(es):