Skip resources if already exist
Problem
This is a (Feature Proposal) Description For bug reports: What went wrong? I had a bug that cloudformation just stuck at UPDATE_ROLLBACK_FAILED. So I should to delete the stack and deploy serverless again. But now I got another problem: [code block] What did you expect should have happened? I think that database is too critical in production level to wont use Retain, In a simple wrong deploy or remove the stack can banish all your tables, wrong deploy can easily rollback but data is really critical. So I suggest to have something like: `serverless deploy --skipResources`, so it wlll skip the resources that already exist and cloudformation wont bring that error. Similar or dependent issues: #3148 Additional Data Serverless Framework Version you're using: 1.6.1 Operating System: Mac OS El Capitan Stack Trace: Provider Error messages*:
Error Output
Error ---------------------------------------
Unverified for your environment
Select your OS to check compatibility.
1 Fix
Solution: Skip resources if already exist
As I said, a bug anywhere could happen, as it did for me. So its not a wrong pattern of management. It can and do happen. So this feature will save a lot of headache if this happen in a prod env.
Trust Score
7 verifications
- 1
As I said, a bug anywhere could happen, as it did for me. So its not a wrong pat
As I said, a bug anywhere could happen, as it did for me. So its not a wrong pattern of management. It can and do happen. So this feature will save a lot of headache if this happen in a prod env.
Validation
Resolved in serverless/serverless GitHub issue #3183. Community reactions: 44 upvotes.
Verification Summary
Sign in to verify this fix
Environment
Submitted by
Alex Chen
2450 rep