Azure / Azure/azure-quickstart-templates
rds-deployment-existing-ad - Existing VNET in its own RG. Deployment fails
- Dominant language
- Bicep
- Stars
- 14.9k
- Forks
- 16.2k
- Avg merge
- 6d 21h
- Merged PRs (30d)
- 6
Description
rds-deployment-existing-ad https://github.com/Azure/azure-quickstart-templates/tree/master/rds-deployment-existing-ad
Trying to deploy this to an existing VNET fails (new NICs cannot find VNET)- I believe it's looking for the VNET in the same resource group I'm creating through the template. The VNET exists in its own RG (I know I can move the resources, but would be cleaner to deploy separately).
Thank you.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the rds-deployment-existing-ad template and its deployment references. Reproduce the deployment with the VNET in a separate resource group, then trace how the template resolves the existing VNET and NIC dependencies. Done means the template deploys successfully without moving the VNET into the newly created resource group.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100