fix: Use computed local.security_group_name in the security group Name tag
#458
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
We should used the already computed
local.security_group_nameinstead ofvar.namein security group rule name tag.Motivation and Context
Its safer to use the local so if the user has decided to set a different name on SG than the EC2 stack.
We are already using it for the SG name tag:
but not on the rules. This will harmonize that too.
Breaking Changes
No breaking changes