chalice delete
See original GitHub issueI love the simplicity of the chalice CLI, but feel there is one more command to add to complete the feature set. That is a chalice delete
(or named something similar) command.
I’m requesting this because chalice deploy
automatically creates the Lambda function, the API Gateway routes and the IAM policy (and perhaps other things). It would be difficult for novice users and frustrating for advanced users to have to manually delete all those things themselves especially for failed experiments and hello word trials which the simplicity of the CLI encourages.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:23
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Quickstart — AWS Chalice
If you're done experimenting with Chalice and you'd like to cleanup, you can use the chalice delete command, and Chalice will delete all...
Read more >Section 0: Introduction to AWS Chalice
Delete the Chalice application¶. Now with an understanding of the basics of how to use AWS Chalice, let's clean up this introduction application...
Read more >chalice - PyPI
If you're done experimenting with Chalice and you'd like to cleanup, you can use the chalice delete command, and Chalice will delete all...
Read more >How to Create CRUD REST API with AWS Chalice - Auth0
Learn how to build a book database API with AWS Chalice serverless technology. ... Now, you will add the code to delete a...
Read more >Develop, deploy, and test micro-services using Chalice on ...
chalise delete ) from the Kernel menu. Run All Cells Command. First, we install Chalice in the kernel using pip
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Agreed, I personally feel this should be managed by a simple CloudFormation template, that way users have the ability to delete the stack from with the AWS UI too if they so desire, and it can be extended upon for future use however the end-user sees fit.
Kind of relates to #35
I agree. Marking as feature request. Thanks for the feedback.