-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Problem about field peer_ip_address
in resource google_compute_router_peer
#4692
Comments
I believe it should be required, but I don't know enough about bgp peers to answer definitively. Is there a reason you would want to create one without a |
I agree that it should be required and I don't want to create one without a |
Yes, it should be required. We are reworking this resource at the moment, and the new version will have the field correctly marked as required. |
@slevenick can you please clarify why It's editable in the API (I guess, it's If it's a mistake, can you please fix it as well? |
I don't believe it is editable because it is assigned when the peer is created. The gcloud command doesn't allow you to specify the ip_address field either: https://cloud.google.com/sdk/gcloud/reference/compute/routers/add-bgp-peer Why do you want to be able to set this field? |
@slevenick it's definitely editable here: I'm setting up Site-to-Site VPN with AWS, the default value provided by GCP is not correct in that case (it's the first address in the subnet). |
I'm not very familiar with that field, and I think it is a separate issue from this one. Feel free to file a request for enhancement to make the |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
Field
peer_ip_address
in resourcegoogle_compute_router_peer
is marked as "Required" in the doc, however, it is "Optional" in the schema. This happens in both GA and Beta. It is pretty confusing and I'm not sure which one I should follow. Could you fix it?The text was updated successfully, but these errors were encountered: