APIGW: fix binaryMediaTypes when importing/updating REST APIs #12586
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.
Motivation
We've recently received a report that binary support for APIGW wasn't working when deploying a REST API through CloudFormation and using the
Body
attribute to use an OpenAPI spec file to define the API.The OpenAPI spec file didn't define binary media types via the
x-amazon-apigateway-binary-media-types
, but it did with the CloudFormation parameterBinaryMediaTypes
.After testing against AWS, it seems the behavior is defined by the
merge
mode when callingPutRestApi
for an existing API, and it will be merged by default with the custom extension when using CloudFormation.Changes
Body
parameterPutRestApi
depending on the merge mode