EMR instance gets "forces new instance" when no changes made #5075
Labels
bug
Addresses a defect in current functionality.
service/emr
Issues and PRs that pertain to the emr service.
Milestone
Code to launch the EMR cluster:
After creation, whenever I try to change other things the EMR cluster is planned for recreation as well although nothing changed there:
If I fill in the
ec2_attributes
with those 3 "missing" attributes everything works correctly and the terraform doesn't attempt to recreate the clusterThe text was updated successfully, but these errors were encountered: