-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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 documentation for md5 auth key #10547
Adding documentation for md5 auth key #10547
Conversation
Hello! I am a robot. Tests will require approval from a repository maintainer to run. @rileykarson, a repository maintainer, has been assigned to review your changes. If you have not received review feedback within 2 business days, please leave a comment on this PR asking them to take a look. You can help make sure that review is quick by doing a self-review and by running impacted tests locally. |
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.
The API docs are kind of rough for this field- they read like internal comments for someone familiar with the resource/feature and not like primary documentation themselves. I have some optional suggestions inline. Not required, though, so feel free to dismiss any/all and I'll approve+merge.
@@ -361,6 +382,17 @@ The following arguments are supported: | |||
BFD declares that a peer is unavailable. If set, the value must | |||
be a value between 5 and 16. | |||
|
|||
<a name="nested_md5_authentication_key"></a>The `md5_authentication_key` block supports: | |||
|
|||
* `name` - |
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.
nit: We could consider dropping Must be referenced by exactly one bgpPeer.
as the schema in Terraform enforces that already- this is implied by just Must be unique within a router.
.
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.
Ack.
@@ -316,6 +335,8 @@ The following arguments are supported: | |||
* `project` - (Optional) The ID of the project in which the resource belongs. | |||
If it is not provided, the provider project is used. | |||
|
|||
* `md5_authentication_key` - (Optional) Present if MD5 authentication is enabled for the peering. |
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.
nit: I think we should deviate from the REST docs on this one based on terminology in https://cloud.google.com/network-connectivity/docs/router/how-to/use-md5-authentication#add-authentication, as the current description fits a proto file and not a REST API (much less a Terraform configuration). I'd suggest something like:
Configuration for MD5 authentication on the BGP session. Structure is [documented below](#nested_md5_authentication_key).
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.
Ack.
Adding documentation for md5_authentication_key field in google_compute_router_peer resource. b/336239032
*Release Note Template for Downstream PRs