-
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
Add fields to InterconnectAttachment to allow for PARTNER interconnects #1323
Add fields to InterconnectAttachment to allow for PARTNER interconnects #1323
Conversation
Looks great. Let me go ahead and get the downstreams generated and we'll take a look! |
I am a robot that works on MagicModules PRs! I built this PR into one or more PRs on other repositories, and when those are closed, this PR will also be merged and closed. |
@ndmckinley I actually found another output status field that's needed. Can I just update this PR? |
c231d05
to
c4a293f
Compare
I reviewed the API spec for the enum fields type and spec, and updated with the full list of options. |
Yep, go ahead and update the PR! I'll just have to do a quick review of each successive commit - just a quick glance. |
Ah, you see that failure under
You should be able to reproduce locally - do you get the same result? |
c4a293f
to
a2b1d44
Compare
@ndmckinley Oops! yeah, indentation issue. Fixed and tested locally! |
On its way through the pipeline! Watch the status indicators below - should show up under |
I am (still) a robot that works on MagicModules PRs! I just wanted to let you know that your changes (as of commit 8b08ffa) have been included in your existing downstream PRs. |
Everything looks green from here :) |
These changes look great to me! I don't have access to an interconnect - could you post the debug logs of creating one of each type of interconnect attachment? If that looks right, I'll approve and this will be out in the next release. |
@ndmckinley I unfortunately don't have a dedicated interconnect either, so I can't set up that type. I have access to a partner interconnect, but can only do the first half of setup for it to go into a pending state, as the second half of setup requires third-party vendor action. |
Bummer! Let me go find someone who's got one. |
Okay, I do have access to someone who's got access to a dedicated interconnect - if you can test the first part of the partner interconnect, by our powers combined (:globe_with_meridians:), we can merge this change. |
Okay, so I created these two objects: resource "google_compute_router" "router1" {
name = "rooter-1"
network = "default"
bgp {
asn = 16550
advertise_mode = "CUSTOM"
advertised_ip_ranges {
range = "10.0.0.0/8"
}
}
}
resource "google_compute_interconnect_attachment" "vlan1" {
name = "vlan1"
type = "PARTNER"
router = "${google_compute_router.router1.name}"
edge_availability_domain = "AVAILABILITY_DOMAIN_1"
} I checked out and compiled hashicorp/terraform-provider-google@75909d7, then used it to Debug log is here: https://gist.github.com/cblecker/f7bfe8030d47035a401564f0514d57eb I've modified the log slightly to substitute the GCP project name, and my google account name from the log. |
Looks great! I'll wait for mine to get back to me and we'll see what we can do. Thank you! |
(The Ansible downstream looks good to me!) |
Okay, almost there! You just need to set |
a2b1d44
to
c0f4975
Compare
@ndmckinley Done! |
I am (still) a robot that works on MagicModules PRs! I just wanted to let you know that your changes (as of commit dd218ee) have been included in your existing downstream PRs. |
Tracked submodules are build/terraform-beta build/terraform build/ansible build/inspec.
c0f4975
to
e95f080
Compare
Great! Well done, thanks for your contribution. |
Thanks for the help in getting this in! One last question: Do you happen to know when the next expected cut of the terraform google provider will be? |
We're working that out now, but if it's more than 2 weeks from now, I'd be surprised. :) |
Sounds great! Thank you! |
This is my first magic-modules PR -- Please let me know if there are additional steps I should take.
ref: hashicorp/terraform-provider-google#2942
cc: @ndmckinley
[all]
[terraform]
[terraform-beta]
[ansible]
[inspec]