Support for adding new tags to instances based on existing ones#51
Open
m0un10 wants to merge 1 commit intoAnswers4AWS:masterfrom
Open
Support for adding new tags to instances based on existing ones#51m0un10 wants to merge 1 commit intoAnswers4AWS:masterfrom
m0un10 wants to merge 1 commit intoAnswers4AWS:masterfrom
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
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.
This PR adds functionality to graffiti monkey to allow for new tags to be added to instances based on existing ones. For example, if our instances were named dev-01 and dev-02, we could add a rule to add an
owner=devmgr@mycompany.comandteam=devtag for any name starting withdev. This is achieved by regular expression rules. For example:Existing functionality is not impacted by this addition. The instance tagging is not triggered unless
_instance_tags_to_add:is included in the configuration. This tagging can be disabled with--noinstances(as per the same convention used for volumes and snapshots) and it supports dry run with--dryrun