fix: Rearranged maps in merge in main.tf:340 for rds aurora security group tags #494
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 lets the user set a custom name tag for aurora security group in
tags
as it is being overridden by the security group name defined. The change is in the order of the maps in the security group tags.Motivation and Context
This change lets module user to set custom name tag for aurora security group instead of the security group name as the value for name tag.
Issue: #492
Breaking Changes
The current changes renames existing Name tag which does not break any existing infrastructure.
How Has This Been Tested?
[ ✅ ] I have tested and validated these changes using one or more of the provided
examples/*
projects[ ✅ ] I have executed
pre-commit run -a
on my pull request