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

Guide to setting up vnet to vnet connection in azure with terraform #8131

Closed
jonathan-kosgei opened this issue Aug 11, 2016 · 5 comments
Closed

Comments

@jonathan-kosgei
Copy link

Is it possible to automate the creation of a vnet to vnet connection between subscriptions on azure with terraform? Has anyone done this before?

@pmcatominey
Copy link
Contributor

Hi @jonathan-kosgei,

Are you referring to Virtual Network Gateways or Virtual Network Peering which just entered public preview recently, or something else?

I've got a mostly-complete PR for Virtual Network Gateways and their Connection resource, I'm waiting for the Azure team to update me on an API issue found while testing.

#8041 is the issue for tracking Virtual Network Peering, you can see there it's currently blocked by the Azure SDK for Go lacking methods to interact with that resource.

@jonathan-kosgei
Copy link
Author

Just read a bit on vnet peering, I'm barely into it trying to grasp the different between azure's classical and resource manager models. I'm looking for a way to connect virtual networks between subscriptions and I'm looking to automate it via terraform. It seems rather daunting so I was wondering if anyone else has ever run into this?

@pmcatominey
Copy link
Contributor

Hi @jonathan-kosgei,

Peering can be used to connect networks between subscriptions, however it cannot link Classic VNets to other Classic VNets.
The requirements and limits are described in the documentation.

If you aren't able to use Peering due to it's limits then you may have to use a Virtual Network Gateway to connect the networks.

Neither of these resources are available in Terraform yet however.

@stack72
Copy link
Contributor

stack72 commented Aug 13, 2016

Closed via #8168

@stack72 stack72 closed this as completed Aug 13, 2016
@ghost
Copy link

ghost commented Apr 23, 2020

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants