-
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
Add support for PARTNER Interconnect VLAN attachments #2942
Comments
@ndmckinley 👋 It looks like you were working on this resource recently.. is exposing the additional API fields to create a partner interconnect complicated? I'd have a look at it myself, but I haven't done much with the Magic Modules stuff. |
Hi there! It's pretty straightforward, and if you have access to an interconnect it'll be easier for you than for me - I haven't got one, so it's tricky to develop. You can use this Cloud Shell environment to do it! |
Added in GoogleCloudPlatform/magic-modules#1323. |
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! |
Community Note
Description
The current feature set for the resource "google_compute_interconnect_attachment" doesn't allow for "partner interconnect", which requires keys "type" and "edgeAvailabilityDomain" from the api. It also requires that the key interconnect to have a set field, which should be left out of the gcloud command or api call.
New or Affected Resource(s)
resource "google_compute_interconnect_attachment"
Potential Terraform Configuration
References
https://www.terraform.io/docs/providers/google/r/compute_interconnect_attachment.html
https://cloud.google.com/sdk/gcloud/reference/compute/interconnects/create
https://cloud.google.com/compute/docs/reference/rest/v1/interconnectAttachments/insert
The text was updated successfully, but these errors were encountered: