-
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
Improve doc accuracy for aws_vpc_security_group_ingress_rule
and `a…
#32148
Improve doc accuracy for aws_vpc_security_group_ingress_rule
and `a…
#32148
Conversation
Community NoteVoting for Prioritization
For Submitters
|
…ws_vpc_security_group_egress_rule` * `ip_protocol` was marked as `Required` in the schema but `Optional` in the docs * `security_group_id` is `Required` but was `Optional` in the schema * Try to clarify the situations where `Optional` arguments are actually `Required` * Make examples less confusing by using a single port; using different ports makes it look like some kind of port mapping
bdf5995
to
ee8af4f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've got a couple of minor suggestions, but overall this looks great to me. Thanks for taking the time to do this!
I saw you'd discussed this a bit on #32089 too. I'm happy to add the commits, but based on what you'd already looked at, could we update the aws_security_group
resource documentation with what you've already written here?
Co-authored-by: Justin Retzolk <[email protected]>
51db979
to
571a5d8
Compare
Sure, I've also updated |
This functionality has been released in v5.6.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. |
…ws_vpc_security_group_egress_rule`
ip_protocol
was marked asRequired
in the schema butOptional
in the docssecurity_group_id
isRequired
but wasOptional
in the schemaOptional
arguments are actuallyRequired
Description
Relations
Closes #29895
Closes #32089
Relates #29893
References
Note that although this technically includes what looks like a breaking change, it's impossible for practitioners to create security group rules without specifying a security group ID so this is actually just a quality-of-life improvement by getting early validation feedback without waiting for the AWS API call to be made.
Output from Acceptance Testing