feat: AWS Instance Scheduler Tagging Support #198
Merged
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.
Description
This change adds a new input variable for the module that allows tags to be applied to the RDS cluster only. Existing functionality with the current tags variable is preserved by using a merge of the two maps.
Motivation and Context
Motivation for adding this new input is that the AWS Instance Scheduler requires tags be added to the RDS cluster only for it to work (i.e. there cannot be a schedule tag added to the RDS instance). Therefore this change is being introduced to allow some tags to specifically be added to the cluster.
Breaking Changes
No breaking changes. This only introduces one new input variable and merges it into the existing tags on the RDS cluster.
How Has This Been Tested?
This change has been tested in development and staging environments and works as expected. AWS Instance Scheduler picks up these tagged clusters and starts/stops them as needed.