Use aws provider level default_tags
configuration
#195
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 even applies to resources created within the cumulus modules, so we no longer need to pass the default tags in through the
tags
variable for thecumulus
anddata-persistence
modules.NOTE: This will generate a terraform diff for existing tagged resources because terraform tracks two separate
tags*
fields.tags
are the resource specific tags which will no longer include the deployment tag whiletags_all
will include the resource specific tags merged together with the provider level defaults. Diffs should show that thetags
field had theDeployment
tag removed, whiletags_all
should remain unchanged (or in some cases have theDeployment
tag added if that resource was not tagged before).