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

Add support for the 'description' field for the aws_security_group_rule resource #16202

Closed
timothykimball opened this issue Sep 27, 2017 · 3 comments

Comments

@timothykimball
Copy link

Hi there,

It would be great to programmatically specify a description for security group rules we create. This will help someone independently auditing understanding why a rule is where it is.

I believe the CLI supports

aws ec2 authorize-security-group-ingress --group-id sg-123abc12 --ip-permissions '[{"IpProtocol": "tcp", "FromPort": 3389, "ToPort": 3389, "IpRanges": [{"CidrIp": "203.0.113.0/24", "Description": "RDP access from NY office"}]}]'

(taken from AWS Documentation: http://docs.aws.amazon.com/cli/latest/reference/ec2/authorize-security-group-ingress.html)

@kwilczynski
Copy link
Contributor

@timothykimball there is work already undergoing to add this functionality, as per:

hashicorp/terraform-provider-aws#1587

I recommend you open issues against the Terraform Providers organisation in an appropriate repository.

@hashibot
Copy link
Contributor

This issue has been automatically migrated to hashicorp/terraform-provider-aws#1780 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to this issue and let us know.

@ghost
Copy link

ghost commented Apr 7, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants