Make responseEndpoint optional #123
Merged
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.
Issue #, if available: #122
Description of changes: While working on #120, went from completely removing responseEndpoint on the first iteration to adding it back in the next time around. Ideally, this should be marked as optional, as it is still sent from CloudFormation's backend. This should work with both
cfn test
and stack provisioning. Will fully test out in the morning before releasing.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.