New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsistent behavior in ServerlessApp cloudformation deployment #708
Comments
Just updating that this issue happened again. The mentioned resources exist in the cloudformation stack but disappeared from the API Gateway resources |
@vasylk Sorry you're experiencing this issue. Could you please provide a full example template so we can try to help troubleshoot? |
@jlhood Just to repeat the behaviour:
The app has continuously been deployed via CodePipeline (Integration with CloudFormation) AWS Region: eu-central-1 Codepipeline template example
Serverless app template
|
+1. I just had this happen with BinaryMediaTypes. My guess is that this is something in CloudFormation. If I edit the CloudFormation template in Designer, adding a new BinaryMediaType, the resulting API has not two but one binary media types. For example, I start with BinaryMediaTypes include "application~1octet-stream". The resulting API has no binary media types. Then, in Designer, I add "image~1gif". Two types in the template. The resulting API has only "image/gif". If I add a third entry, before "image~1gif", and it reads "application~1octet-stream" (that is, my BinaryMediaTypes entry now lists "application~1octet-stream", "image~1gif", "application~1octet-stream"), I get no errors and the resulting API has no binary media types. |
@brooksidesw Your issue seems to be related to this pr #954 which is staged for release. @vasylk There are two ways to define Api gateway resources in cloudformation: 1. defining an explicit swagger doc in |
Hello,
we have been experiencing unexpected? behavior affecting API Gateway when deploying the serverless app.
Along with SAM resources the cloudformation template contains API Gateway proxy integration with S3 (see simplified Cloudformation sippet for reference).
The stack is deployed via CodePipeline + integration with CloudFormation
AWS::Region = eu-central-1
The unexpected behavior is:
The same happens with BinaryMediaTypes property of AWS::Serverless::Api
It gets restored when we manually comment out these resources in CloudFormation template and run two deployments in a row - without these resources in the template and with them. I assume it is not expected behavior.
We have to manually run Deploy API action in API Gateway to get these changes available.
Regards
Vasyl
Template Snippet:
The text was updated successfully, but these errors were encountered: