-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Stage feature not functioning as expected #470
Labels
Comments
Thanks for reporting. We'll get that fixed. |
achautha
pushed a commit
to achautha/chalice
that referenced
this issue
Aug 12, 2017
stealthycoin
pushed a commit
to stealthycoin/chalice
that referenced
this issue
Aug 14, 2017
stealthycoin
added a commit
to stealthycoin/chalice
that referenced
this issue
Aug 14, 2017
The API Gateway stage is not set correctly since it was renamed from dev to api. This change enforces the 'api' default all the way through the config layer and CLI layer rather than making the end code that consumes the configuration manually enforce a default everywhere the api gateway stage name is used. fixes aws#470
stealthycoin
added a commit
to stealthycoin/chalice
that referenced
this issue
Aug 14, 2017
The API Gateway stage is not set correctly since it was renamed from dev to api. This change enforces the 'api' default all the way through the config layer and CLI layer rather than making the end code that consumes the configuration manually enforce a default everywhere the api gateway stage name is used. fixes aws#470
stealthycoin
added a commit
to stealthycoin/chalice
that referenced
this issue
Aug 14, 2017
The API Gateway stage is not set correctly since it was renamed from dev to api. This change enforces the 'api' default all the way through the config layer and CLI layer rather than making the end code that consumes the configuration manually enforce a default everywhere the api gateway stage name is used. fixes aws#470
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When attempting to use
chalice deploy --stage dev
the dev API Gateway is given the /api context and when usingchalice deploy --stage prod
the Prod API Gateway is given the /dev context. It appears order does not matter and I've deleted and started from scratch and still seeing issue. #The text was updated successfully, but these errors were encountered: