Skip to content
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 to associate a vlan_attachment to a router-interface #2116

Closed
netturpin opened this issue Sep 26, 2018 · 4 comments · Fixed by GoogleCloudPlatform/magic-modules#1830
Assignees
Labels

Comments

@netturpin
Copy link

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment. If the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.

Description

Based on GCP documentation, there are 4 steps to get a complete setup :
1 Request a Partner/Dedicated Interconect (out of scope as mention in issue #1140 )
2. Create a vlan attachment (solved with #1569)
3. Associate a vlan attachment with a cloud router by creating a router interface linked to the vlan attachment
4. Setup a BGP session between the Cloud router and the on-prem router.

My understanding is, now that we are able to create vlan attachment in terraform, we need the ability to specify them when we create a router_interface. I feel this should be done in google_compute_router_interface object but I may be wrong,

The BGP session setup should be already functional with the compute_router_peer object.

New or Affected Resource(s)

  • google_compute_router_interface

Potential Terraform Configuration

# Propose what you think the configuration to take advantage of this feature should look like.
# We may not use it verbatim, but it's helpful in understanding your intent.
resource "google_compute_router_interface" "foobar" {
  name       = "interface-1"
  router     = "router-1"
  region     = "us-central1"
  ip_range   = "169.254.1.1/30"
  vlan_attachment = "attachment-1"
}

References

@morgante
Copy link

Along with this, the "cloudRouterIpAddress" field needs to be exposed as an output from an interconnect attachment: https://cloud.google.com/compute/docs/reference/rest/v1/interconnectAttachments/get

@morgante
Copy link

@tysen Have we also addressed this comment as well?

@tysen
Copy link

tysen commented May 24, 2019

Sure have.

@ghost
Copy link

ghost commented Jun 24, 2019

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 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked and limited conversation to collaborators Jun 24, 2019
@github-actions github-actions bot added forward/review In review; remove label to forward service/compute-router labels Jan 15, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants