Add ownerID as fields to a variety of ec2/vpc resources #964
Conversation
This file contains 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
|
I think this is a good change, what do you think @der-eismann @svenwltr? Problem is probably that we will need this on more resources afterwards. Also please run |
der-eismann
approved these changes
Aug 25, 2023
svenwltr
approved these changes
Aug 25, 2023
|
Hey @der-eismann, thanks for merging this in! Is it possible for this to get released too? Thanks :) |
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.
Allows users of aws-nuke to be able to exclude AWS RAM shared VPC resources from being nuked by exposing
ownerIDas a field from various VPC resources.