Bug Fix - API Gateway template doesn't explicitly state defaults, so old configurations remain #153
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… overrides for API gateway stage method configurations
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The Cloudformation template for API Gateway staging was not including explicitly configured settings if those settings matched one of the defaults.
This was causing issues when trying to go from
dataTraceEnabled: trueback todataTraceEnabled: false(the default setting). The template was not including thedataTraceEnabled: false. Therefore the API gateway stage configuration was remainingdataTraceEnabled: true.Getting this PR out there while I have a few minutes. I will add more context later, if needed.