tasks.json: Start local tunnel using custom port changes

[stokedout]

Describe the bug

I noticed that when running Debug (Chrome) and thus triggering tasks.json Start local tunnel using a custom port that the dev-tunnel is created with that port number too but if left as default 3978 it doesn't. For example:

Port left as default yields 80 -> 3987

Forwarding URL https://95wms5cg.euw.devtunnels.ms/ to http://localhost:3978 and saved [BOT_DOMAIN, BOT_ENDPOINT] to /Users/stokedout/src/play/TeamsCustom/bot-conversation-python_2/env/.env.local.

# env.local
...
BOT_ENDPOINT=https://95wms5cg.euw.devtunnels.ms
...

Port changed to 8000 yields 8000 > 8000

Forwarding URL https://95wms5cg.euw.devtunnels.ms:8000/ to http://localhost:8000 and saved [BOT_DOMAIN, BOT_ENDPOINT] to /Users/stokedout/src/play/TeamsCustom/bot-conversation-python_2/env/.env.local.

Resulting service endpoint in Azurd: https://95wms5cg.euw.devtunnels.ms ✔️

# env.local
...
BOT_ENDPOINT=https://95wms5cg.euw.devtunnels.ms:8000
...

To Reproduce
Steps to reproduce the behavior:

• I want to use port 8000 since I'm hosting the bot code in a django backend
• As suggested in 2. Change port of the README I changed the port from 3978 to 8000
• Run: Debug (Chrome)
• Type and send a message
• Nothing received or logged in the backend

Resulting service endpoint in Azure: https://95wms5cg.euw.devtunnels.ms ❌

The way I made it work was manually adding the port in the Azure bot endpoint as https://95wms5cg.euw.devtunnels.ms:8000

Expected behavior

Mapping a custom port should either create the tunnel the same way the default one is or set the port in Azure.

Screenshots
If applicable, add screenshots to help explain your problem.

VS Code Extension Information (please complete the following information):

• OS: macOS
• Version Sonoma 14.4.1 (23E224)

CLI Information (please complete the following information):

• OS: Vs code teams toolkit extension
• Version v5.8.1

Additional context
Add any other context about the problem here.

[microsoft-github-policy-service]

Thank you for contacting us! Any issue or feedback from you is quite important to us. We will do our best to fully respond to your issue as soon as possible. Sometimes additional investigations may be needed, we will usually get back to you within 2 days by adding comments to this issue. Please stay tuned.