resource/aws_ecs_task_definition: prevent spurious container definition diffs #36029
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.
Description
When the order of the container definitions does not match between AWS API and aws_ecs_task_definition, terraform tries to replace the task definition to match the container definitions order. This is unnecessary as the container order does not mean anything.
I am trying to to import bunch of different task definitions using a single module, and I keep getting diffs due to container definitions order. This PR prevents unnecessary diffs for when the container definitions order does not match between API and Terraform.
Relations
Relates #11463.
Relates #35792.