Azure / Azure/bicep

Add private endpoint URLs to `environment()` response

Open
#9,839 7 comments 11 reactions 0 assignees View on GitHub
enhancement
Dominant language
Bicep
Stars
3.6k
Forks
830
Avg merge
1d 21m
Merged PRs (30d)
79

Description

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](https://github.com/Azure/bicep/issues/url).
* 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.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the context in #9708 and the environment() function behavior described in this issue. Identify the private DNS equivalents for the relevant resource providers and define the complete set of private endpoint URLs that the response should expose; the work is done when those suffixes are returned correctly and the documented Key Vault case no longer produces the wrong zone.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cloud, infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.