You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 1, 2018. It is now read-only.
When I was updating the request template for the API Gateway passthrough method, I noticed that the method was not updating between CloudFormation updates. The updates only went into effect if I deleted and recreated the stack.
I think this can be avoided by creating a random resource name each time the stack is updated. This forces the original resource to be deleted, and the new resource to be created.
The text was updated successfully, but these errors were encountered:
I was also having StageName problems when trying to update the stack. Errors like this: 16:28:04Z us-east-1: CREATE_FAILED Deploymentbdcec9d2: StageDescription cannot be specified when stage referenced by StageName already exists. The way that I evaded these, in the end, was to use the random deployment name as part of the deployment's stage name — so it also changed with each update.
When I was updating the request template for the API Gateway passthrough method, I noticed that the method was not updating between CloudFormation updates. The updates only went into effect if I deleted and recreated the stack.
I think this can be avoided by creating a random resource name each time the stack is updated. This forces the original resource to be deleted, and the new resource to be created.
The text was updated successfully, but these errors were encountered: