Azure / Azure/azure-functions-core-tools
Debugging function that connects to an endpoint that uses Private Link / Private Endpoint
- Dominant language
- C#
- Stars
- 1.5k
- Forks
- 498
- Avg merge
- 4d 20h
- Merged PRs (30d)
- 14
Description
I'm trying to debug a function that connects to Azure Service Bus that uses a private endpoint.
I've spun up a VM and peered the VNets and successfully tested connectivity using the Service Bus SDK. But when trying to debug a function in VS code / core tools V3, the function trigger cannot connect to the Service Bus queue.
I've tried added WEBSITE_VNET_ROUTE_ALL: 1 and WEBSITE_DNS_SERVER: 168.63.129.16 to the app setting but still no connectivity.
Does core tools support private endpoint? Is the a way to get this working?
Contributor guide
Research direction
The report concerns Azure Functions Core Tools V3 debugging in VS Code, an Azure Service Bus queue, and a private endpoint. Start by reproducing the trigger connection with the reported VNet peering, WEBSITE_VNET_ROUTE_ALL, and WEBSITE_DNS_SERVER settings; done would require a confirmed support determination and a documented or implemented path to working connectivity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, vscode
- Domain
- cli, cloud, networking
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100