Added the tag_cluster_resources policy #692
Draft
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
athiruma
force-pushed
the
modify_tagging_resources
branch
from
09a1259 to
eb258e7
Compare
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.
Type of change
Note: Fill x in []
Description
Added the tag_cluster_resources policy in the approach.
Approach:
Note: Added the OptionalTags env var: ['Owner', 'Manager', 'Project', 'Environment']. This helps this can use any account without adding NA values to these keys.
By following the above approach we can tag all the resources that belong to the cluster in a single click.
Reference:
ResourceGroupTagging: Link1, Link2
For security reasons, all pull requests need to be approved first before running any automated CI