Skip to content
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

Closed
stewmi opened this issue Aug 11, 2017 · 1 comment · Fixed by #475
Closed

Stage feature not functioning as expected #470

stewmi opened this issue Aug 11, 2017 · 1 comment · Fixed by #475
Labels

Comments

@stewmi
Copy link

stewmi commented Aug 11, 2017

When attempting to use chalice deploy --stage dev the dev API Gateway is given the /api context and when using chalice 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. #

@jamesls
Copy link
Member

jamesls commented Aug 11, 2017

Thanks for reporting. We'll get that fixed.

@jamesls jamesls added the bug label Aug 11, 2017
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
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants