[AVM Module Issue]: Private endpoint not being created in correct resource group in the latest sql server module 0.12.1

[corey-at-digizoo]

Check for previous/existing GitHub issues

• I have checked for previous/existing GitHub issues

Issue Type?

Bug

Module Name

avm/res/sql/server

(Optional) Module Version

0.12.1

Description

I'm upgrading from using avm/res/sql/server version 0.8.0 -> 0.12.1 and I have noticed that the private endpoint is not being created in the correct resource group as defined by either the resourceGroupResourceId parameter, or in the case this parameter is not provided, the resource group which contains the virtual network subnet linked to that private endpoint.

From a code perspective it's most likely related to scope defined on the private endpoint sub module but I can't determine why it's not creating the private endpoint in the desired resource group.
I have tried:
a) Specifying resourceGroupResourceId parameter
b) Not specifying resourceGroupResourceId parameter, in which case it should be created in the resource group of the linked subnet

In either case, the private endpoint is being created in the same resource group as the sql server.

Kind regards,
Corey

(Optional) Correlation Id

No response

[microsoft-github-policy-service]

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Tip

For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation.

[avm-team-linter]

@corey-at-digizoo, thanks for submitting this issue for the avm/res/sql/server module!

Important

A member of the @Azure/avm-res-sql-server-module-owners-bicep or @Azure/avm-res-sql-server-module-contributors-bicep team will review it soon!

[peterbud]

Seems similar to #4257? PEP deployment is done using the common AVM module, I'll check it.

[microsoft-github-policy-service]

Warning

Tagging the AVM Core Team (@Azure/avm-core-team-technical-bicep) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.

Tip

• To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
• To avoid this rule being (re)triggered, the ""Needs: Triage 🔍" label must be removed as part of the triage process (when the issue is first responded to)!

[peterbud]

Confirmed the issue. PEP deployment is not respecting the specified resource group ID.

[corey-at-digizoo]

Thanks @peterbud, yes it looks like the same issue as the the one you linked. Apologies, I did have a look through the open issues but I must have missed this one.

[peterbud]

Thanks @peterbud, yes it looks like the same issue as the the one you linked. Apologies, I did have a look through the open issues but I must have missed this one.

Actually you helped a lot to realize that this is not an isolated problem, but something that is impacting multiple modules. PR is on it's way: #4421