fix: Missing field LogConfiguration.LogDriver error when enable_cloudwatch_logging is false #91
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
If we pass
enable_cloudwatch_logging = false
on a servicecontainer_definitions
section, it will generate this error below:Motivation and Context
This behavior happens because in the planning phase the
logConfiguration
is computed as{}
, which is an invalid configuration when posting on AWS API.My
plan
of a just imported resource is:And this is computed this way because of a
merge()
:In the console, if all parameters to merge are null or empty, the result is an empty object:
Breaking Changes
No breaking change
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull request