add prevent destruction policy and function #158
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
cneralich
reviewed
Oct 16, 2019
|
|
||
| for found_resources as address, r { | ||
| if r.destroy and not r.requires_new { | ||
| print("You are trying to destroy a blacklisted resource", address, "of type", type) |
There was a problem hiding this comment.
This print statement follows a slightly different convention than the one in the example policy, which reads:
"You are trying to destroy a resource", address, "of blacklisted type", type
Neralich
approved these changes
Oct 17, 2019
cneralich
approved these changes
Oct 17, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added new prevent-destruction-of-blacklisted-resources.sentinel with a common function it uses which is validate_destroy_resources.sentinel. The new policy has associated test cases for Terraform 0.11 and 0.12.
Note that this policy is truly cloud-agnostic since it blacklists network resources from AWS, Azure, and GCP.