-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
security_group_rule: explictly state that a single resource can manage many security group rules. #27005
Conversation
Explicitly document that a single security group rule resource may result in the EC2 API creating one or many security group rule(s) depending on whether multiple source(s)/destination(s) are provided or whether a source/destination has a list containing multiple elements.
Community NoteVoting for Prioritization
For Submitters
|
Relates #20104. |
I think the |
@ewbankkit I simplified my change. the linter should pass now. |
@ewbankkit do you have any idea why this GA check is failing? This seems like a really small change and should not be failing |
LGTM 🚀 Thanks @aidanmelen! |
This functionality has been released in v4.35.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Explicitly document that a single security group rule resource may result in the EC2 API creating one or many security group rule(s) depending on whether multiple source(s)/destination(s) are provided or whether a source/destination has a list containing multiple elements.
Description
The security group rule resource explicit states that it "Represents a single ingress or egress group rule" which is false.
For example:
Relations
#25173