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
AWS API Gateway: Allow stage customization #8346
Comments
@nl-brett-stime sounds reasonable to me |
medikoo
changed the title
Allow using a different stage for API Gateway than the Serverless stage option
AWS API Gateway: Allow stage customization
Nov 30, 2020
@medikoo I would like to pick this up if it is already not done. Can you assign it to me? |
@pavanandhukuri sure. PR's welcome! |
Raised a PR #11487 |
@medikoo I missed tagging the PR with |
@pavanandhukuri indeed, thanks for reminder! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Use case description
API Gateway has a feature to manage different stages (dev/qa/prod). However, some users have their stages split across different AWS accounts. Other users may manage stages via IaC tools such as Cloud Formation, Terraform and Serverless. In these cases, API Gateway's stage feature becomes redundant: https://stackoverflow.com/a/53652722/93345
Proposed solution
Allow the stage value sent to API Gateway to differ from Serverless' stage but fall back to Serverless' stage as a default value.
E.g.,
The text was updated successfully, but these errors were encountered: