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.
Add validation check for UpdateReplacePolicy
See original GitHub issuecfn-lint version: 0.22.4
Description of issue. After getting bit by a missing UpdateReplacePolicy while adding a ddb local index, I think it would be good to include a check about including an UpdateReplacePolicy, similar to what is done for DeletionPolicy. These sort of warnings, at least in my experience, are great for pointing out features/practices that are easy to miss when getting started, but could save a whole lot of grief if configured.
Cfn-lint uses the CloudFormation Resource Specifications as the base to do validation. These files are included as part of the application version. Please update to the latest version of cfn-lint or update the spec files manually (cfn-lint -u)
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:7 (6 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
Probably? You’d might like to have a UpdateReplacePolicy, but no DeletionPolicy because Deletion is a more explicit action than a UpdateReplacement (aka it’s easier to trigger an UpdateReplacement by accident). But being explicit about those cases isn’t bad either. Adding
DeletionPolicy: Deletewould make the warning disappear.Or warn for a resource with a DeletionPolicy but no UpdateReplacePolicy?