bug report: provision fails with DownloadBicepCliError

[nanddeepn]

While trying to provision a bot from Teams Toolkit extension for VS Code, we get below error:

Failed to Execute lifecycle provision due to failed action: arm/deploy. DownloadBicepCliError:Unable to download Bicep cli from 'https://api.github.com/repos/Azure/bicep/releases'. The error message was: read ECONNRESET. Fix the error and try again. Or remove the bicepCliVersion config in the config file teamsapp.yml and Teams Toolkit will use bicep CLI in PATH.

Please suggest.

Expected behavior
The bot should be provisioned without error.

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

• OS: Windows
• Version 5.0.0

[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.

[xzf0587]

Hi @nanddeepn,
Thanks for reaching out.
The message showed that the TTK failed to download Bicep cli from 'https://api.github.com/repos/Azure/bicep/releases'. The Bicep cli is used to compile the bicep file under infra folder when executing Provision command.
Since the error message said that read ECONNRESET when download process, could you verify whether you can access 'https://api.github.com/repos/Azure/bicep/releases'?

If the network cannot access the download url as design, please follow the steps to config Bicep cli.

1. Download Bicep cli from https://github.com/Azure/bicep/releases
2. Add the Bicep cli path into PATH environment.
3. Remove the line including the BicepCliVersion in teamsapp.yml as below.
   

[microsoft-github-policy-service]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

[microsoft-github-policy-service]

Due to lack of details for further investigation, we will archive the issue for now. In case you still have following-up questions on this issue, please always feel free to reopen the issue by clicking ‘reopen issue’ button below the comment box. We will get back to you as soon as possible.