Add private endpoint URLs to `environment()` response

alex-frankel commented 1 year ago

Context from #9708:

When leveraging the environment function, 'privatelink${environment().suffixes.keyvaultDns}', to deploy a Private DNS Zone for the Azure Key Vault Private Endpoint, the following suffix is retrieved: "keyvaultDns": ".vault.azure.net". That is verified at this link - https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/bicep-functions-deployment#example-1.
The proper Private DNS Zone for Key Vault Private Endpoints is actually privatelink.vaultcore.azure.net. If 'privatelink${environment().suffixes.keyvaultDns}' is defined in the template, the zone privatelink.vault.azure.net is created instead.

Presumably there are other private DNS equivalents for other resource providers, so we should do all of them at once.

rebel24 commented 1 year ago

Just spent a day on this due to this issue? Will this be resolved in the future so other people won't get this issue. With this issue the A records do not generate from the dnsgroup if you are using the wrong URL

aavdberg commented 8 months ago

I have the same problem and spend a lot of time on it before I figured it out that the suffix is wrong.

@alex-frankel when this will be fixed?

bgawale commented 6 months ago

Any update on this please? Still facing the same issue with key vault name suffix.

aavdberg commented 2 months ago

@alex-frankel is the team looking at this and what is the status.

Azure / bicep

Add private endpoint URLs to `environment()` response #9839