Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Ignore check for unchanged files after failed deployment
See original GitHub issueAfter a failed deployment due to remote (CloudFormation) error I have to use sls deploy --force to trigger a new deployment with the same configuration because serverless skips the deployment with the Service files not changed. Skipping deployment... notice per default.
Expected behaviour
If a deployment failed due to a remote (CloudFormation) error, a new sls deploy should trigger a deployment even if the service files have not changed. The check for unchanged configuration should only matter after a successful deployment.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:50
- Comments:13 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Have you tried to use
sls deploy --force@tom10271 ?+1 Bump on this issue. Serverless should be able to clean up failed deployments. Using
--forcedoesn’t seem like a very stable solution.