Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

adding tag\name for a rule #327

Open
avishni01 opened this issue Sep 3, 2024 · 6 comments
Open

adding tag\name for a rule #327

avishni01 opened this issue Sep 3, 2024 · 6 comments

Comments

@avishni01
Copy link

hello

i have just start using the module instead of creating with the basic terraform resources. it took me time to use it correctly , but one thing is missing (or maybe i didn't find how to do it), naming the SG rules. the name is actully bases on the tag Name, vurrntly in the default view all rules are displayed with empty name , there should be an option to add tags and name to for each rule.

@FlorinAndrei
Copy link

Yeah, there might be issues when names are conflicting with each other, but this would be very useful. I actually found this ticket because I was looking for a way to tag or describe the rules.

@ScubaDrew
Copy link

This module is not that great. Adding/Changing rules never works correctly either.

@tigpt
Copy link

tigpt commented Oct 29, 2024

I also wanted to add tags to the SG Rules, but looking at hashicorp/aws and hashicorp/awscc this is not exposed in api yet, so we can't do this for the module.

Looking forward to be able to track SG Rules with Tags to make sure every SG Rule is terraform and not clicksops.

@robertalexa
Copy link

According to documentation, it think it is just a case of using a different resource for rules
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/security_group_rule

Please note the first note:
image

I interpret that as the module (this as well as others e.g. ecs) to drop the use of aws_security_group_rule and switch to aws_vpc_security_group_egress_rule and aws_vpc_security_group_ingress_rule respectively.

Wondering if maybe @antonbabenko or @bryantbiggs know anything on this or are tracking this on their roadmap already.

Copy link

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label Dec 12, 2024
@tomasz-baran
Copy link

tomasz-baran commented Dec 12, 2024

not stale

@github-actions github-actions bot removed the stale label Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants