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

Fix API Gateway stage not being set correctly #475

Merged
merged 3 commits into from
Aug 14, 2017

Conversation

stealthycoin
Copy link
Contributor

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 #470

@achautha Thanks for the contribution. I added a few more tests and more strict defaults in the Config object itself.

closes #474

@codecov-io
Copy link

codecov-io commented Aug 14, 2017

Codecov Report

Merging #475 into master will decrease coverage by 0.03%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #475      +/-   ##
==========================================
- Coverage   94.01%   93.98%   -0.04%     
==========================================
  Files          18       18              
  Lines        2940     2941       +1     
  Branches      380      380              
==========================================
  Hits         2764     2764              
  Misses        129      129              
- Partials       47       48       +1
Impacted Files Coverage Δ
chalice/deploy/deployer.py 93.89% <100%> (ø) ⬆️
chalice/cli/__init__.py 81.86% <100%> (ø) ⬆️
chalice/cli/factory.py 88.57% <100%> (-0.86%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8313fd0...ccce980. Read the comment docs.

Copy link
Member

@jamesls jamesls left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't forget to add a changelog entry. Otherwise looks good.

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 stealthycoin merged commit 49b7946 into aws:master Aug 14, 2017
@stealthycoin stealthycoin deleted the fix-stages branch August 14, 2017 21:26
stealthycoin added a commit that referenced this pull request Aug 14, 2017
Fix API Gateway stage not being set correctly
@jasonrhaas
Copy link

Just ran into this problem. Any idea when the fix will get pushed to a new PyPi release?

@jamesls
Copy link
Member

jamesls commented Aug 16, 2017

Version 1.0.1, which includes this fix, was just released on pypi.

@johntmyers
Copy link
Contributor

I'm using 1.0.1 and within config.json, api_gateway_stage is totally ignored and api is used. I currently have to use the --api-gateway-stage option to force the actual stage I want.

@jamesls
Copy link
Member

jamesls commented Aug 25, 2017

@johntmyers Thanks for reporting, I've created an issue to track this here: #495

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Stage feature not functioning as expected
5 participants