Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Allow creating a VM on an existing vnet instead of creating one
See original GitHub issueThe vm resource currently always creates a dedicated vnet and subnet. It would be very useful to be able to instead only give a subnet resource name, which can be an existing one (or created separately).
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:7 (5 by maintainers)
Top Results From Across the Web
I can't attach my new VM to my already created Vnet
I have a Vnet created (vnet001) in a resource group (resourses-rg) ... me the Vnet (vnet001), instead Azure force to me a create...
Read more >Creating VM in existing Vnet. Cant see existing Vnet
1 Answer. Make sure that you create new VM in the same region where your VNET is located.
Read more >Virtual networks and virtual machines in Azure
When you create a virtual machine (VM), you create a virtual network or use an existing one. Decide how your virtual machines are...
Read more >ARM template to create a VM using an existing VNet and ...
According to the changes, the template will use the existing VNet and subnet instead of creating new ones. Share.
Read more >Configure the Required Virtual Network in Microsoft Azure
Microsoft Azure requires creating one subnet when creating a VNet. You can either retain the default values or customize the name and range....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
That’s more or less the conclusion I came up to yesterday when I was trying to add this. The VM needs to know the subnet, and the subnet is created as part of the vnet. I’ll finish it off this weekend and PR in.
Cool, I’ll merge that in then!