fix: Separate db_instance_tags
from merged tags
sub-module input
#544
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 PR splits the two on input so that the
var.db_instance_tags
are only applied to the rds_db_instance, preserving the functionality that ifvar.tags
is defined, it will be merged withvar.db_instance_tags
Motivation and Context
This change is required because it incorrectly maps
var.db_instance_tags
to all resources associated with the module. This functionality is reserved for thevar.tags
input.var.db_instance_profile
described as "Additional tags for the DB instance", only these tags should be associated with therds_db_instance
Breaking Changes
None - backwards compatible since
var.db_instance_tags
andvar.tags
are still merged onthis.db_instance
when present.How Has This Been Tested?
I need to test these changes, we have an existing project that this might be applicable in.
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull request