[AVM Module Issue]: Unable to create private endpoints for Private Link Scope when VNet is in different subscription #3835
Labels
Class: Resource Module 📦
This is a resource module
Needs: Triage 🔍
Maintainers need to triage still
Status: Response Overdue 🚩
When an issue/PR has not been responded to for X amount of days
Type: AVM 🅰️ ✌️ Ⓜ️
This is an AVM related issue
Type: Bug 🐛
Something isn't working
Check for previous/existing GitHub issues
Issue Type?
Bug
Module Name
avm/res/insights/private-link-scope
(Optional) Module Version
0.5.2
Description
A deployment failure happens when the Private Link Scope resource is in a different subscription to the Virtual Network.
Generally the error is
ResourceGroupNotFound
on the private endpoint resource group (since it exists in a different subscription). If a resource group happens to exist with the same name in the PLS subscription, then the deployment produces anInvalidResourceReference
.Private Endpoints must be provisioned in the same subscription as the Virtual Network they are connected to. Whilst this module allows you to customise the resource group for the private endpoint, it currently assumes the same subscription as the Private Link Scope resource.
To avoid needing another parameter, perhaps the scope on this line should infer the subscription from the subnet resource ID?
bicep-registry-modules/avm/res/insights/private-link-scope/main.bicep
Line 160 in 8ee8adb
(Optional) Correlation Id
No response
The text was updated successfully, but these errors were encountered: