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

Updating a route's URL doesn't delete old resource #305

Closed
budowski opened this issue Apr 25, 2017 · 1 comment
Closed

Updating a route's URL doesn't delete old resource #305

budowski opened this issue Apr 25, 2017 · 1 comment
Labels

Comments

@budowski
Copy link

When I update a route's URL, the old resource (for the old URL) is not deleted.

This might be a hard-to-solve issue - maybe save a local cache of function/URL mapping, and when the URL changes (assuming function name stays the same), chalice deploy will delete the old resources.

@jamesls
Copy link
Member

jamesls commented Apr 25, 2017

I think I see the issue. The internals recently changed to first generate a swagger API and then import/update the api gateway API (as opposed to making individual API calls for each route).

The default setting is merge for put_rest_api, but it needs to be overwrite. Should be a quick fix Thanks for reporting.

@jamesls jamesls added the bug label Apr 25, 2017
jamesls added a commit to jamesls/chalice that referenced this issue May 1, 2017
This tests that redeploys work as expected.
Helps to prevent issues like
aws#305
from regressing again.
jamesls added a commit to jamesls/chalice that referenced this issue May 1, 2017
This tests that redeploys work as expected.
Helps to prevent issues like
aws#305
from regressing again.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants