provider/aws: Validate aws_ecs_task_definition.container_definitions #12161
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.
Currently there is no validation in
aws_ecs_task_definition.container_definitions
,but I would like to be able to validate it at plan.
The following is an example for invalid definition.
Note that
"sleep 360"
incommand
should be array as["sleep", "360"]
.This is easy to make a mistake. I was actually wrong and suffer for a while.
Before change
There is no error at plan. ( Of course, it will be an error when applied. )
After change
We can now detect the error at plan:
Furthermore, field names that failed in
json.Unmarshal
are now included in error messages thanks to recent update of terraform Go version to 1.8.