Introduce wg_tags to handle default_tags on provider level #1653
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.
PR o'clock
closes: #1578, #1455(?), #1248(?)
Description
When default_tags are used on aws provider level, and the same tags are defined as input to this module, we end up with this issue:
default_tags always shows an update
If "tags" var is not set, no tags will be applied to resources which defines tag_specification.
So, either we have default_tags and do not set "tags". which leaves us with "empty" tag_specifications or we don't use default_tags.
This PR introduces new variable "wg_tags", which will be used on resources which define dynamic tags/tag_specifications if "tags" is not set. Backward compatibility is therefore fully retained.
There will be changes only if wg_tags is set, otherwise the module works the same as before.
Checklist