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

azure_virtual_network can't assign custom Resource Group #3266

Closed
spuder opened this issue Sep 17, 2015 · 5 comments
Closed

azure_virtual_network can't assign custom Resource Group #3266

spuder opened this issue Sep 17, 2015 · 5 comments

Comments

@spuder
Copy link
Contributor

spuder commented Sep 17, 2015

There currently is no way (as far as I can tell) to create a network and assign it to a resource group.

resource "azure_virtual_network" "mail-network" {
  "name" = "mail-network"
  address_space = ["172.16.0.0/24"]
  location = "West US"
  subnet {
     "name" = "subnet1"
     "address_prefix" = "172.16.0.0/28"
  }
}

screenshot 2015-09-17 13 29 41


If you create a network through the web interface, selecting a resource group is required.

screenshot 2015-09-17 13 31 43

Here is the api documentation.

https://msdn.microsoft.com/en-us/library/azure/mt163661.aspx

The query should look like this:

 https://management.azure.com/subscriptions/{subscription-id}/resourceGroups/{resource-group-name}/providers/microsoft.network/virtualNetworks/{virtual-network-name}?api-version={api-version}
@spuder spuder changed the title Azure networking allow custom resource group azure_virtual_network can't assign custom Resource Group Sep 17, 2015
@spuder
Copy link
Contributor Author

spuder commented Sep 21, 2015

Additionally, it appears that the azure_virtual_network uses the clasic syntax.
screenshot 2015-09-21 14 33 21

@spuder
Copy link
Contributor Author

spuder commented Sep 21, 2015

Related to #3212

@dcarley
Copy link
Contributor

dcarley commented Sep 28, 2015

Also related to #3089 and #3097

@phinze
Copy link
Contributor

phinze commented Oct 12, 2015

Thanks for the report, @spuder - closing this thread since I believe we have this covered in the linked issues.

@phinze phinze closed this as completed Oct 12, 2015
@ghost
Copy link

ghost commented Apr 30, 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 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants