-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSL: CERTIFICATE_VERIFY_FAILED error on "az bicep install" Resurfaced #20842
Comments
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @armleads-azure. Issue DetailsDescribe the bug To Reproduce
With debug:
Expected behavior Environment summary
Additional context
|
route to service team |
As a temporary workaround, you can install bicep manually outside the az cli following the instructions here: https://docs.microsoft.com/en-us/azure/azure-resource-manager/bicep/install#install-manually This however does not allow you to deploy bicep from the az cli though |
Also experiencing this in version 2.32.0 behind a corporate proxy. |
I have also confirmed that this issue exists in version 2.32.0. I posted additional details in my comment on the previously-closed issue, #19420. Unfortunately, this is a showstopper that prevents me from adopting bicep in a corporate setting at the moment, which is a shame - the DSL and tooling offered appear to be a great evolution & streamlining of the ARM template approach! |
Upon inspecting the previous commit for #19420, the issue is that the bicep module is hardcoded to use the default @Zerthick and @Jaffacakes82 - in the meantime, I found another workaround that allowed Append your corporate proxy certificate(s) to the end of the certifi library's
|
Thanks for this - worked for me. In case it helps others: I'm on a mac and found the correct
and subsequently found the right |
These suggestions work for us and provide a temporary workaround, for anyone looking to run Bicep from a Docker container (such as VS devcontainers) we use the following solution (with the cert fix that @jtrivett mentions)
|
@Zerthick Apologies for the late reply. Could you please let us know if you have been able to test using the above mentioned suggestions ? Please let us know if you are still running into the same issue. Awaiting your reply. |
@navba-MSFT The suggestions above do indeed appear to work, though as others on this ticket have commented they are a workaround, bicep should be ideally obeying the |
Thanks @ssvalkyrie & @jtrivett, worked a treat. @navba-MSFT, agree with @Zerthick, this needs addressing by Microsoft. |
@navba-MSFT thanks for checking in on this issue. Is this something that can be reviewed & prioritized by Microsoft for an upcoming AZ CLI release? Us corporate users would greatly appreciate it! |
@navba-MSFT Yeah, let us know what is the plan. As mentioned before there is a lot of people behind a corporate firewall. |
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @josephkwchan, @jennyhunter-msft. Issue DetailsDescribe the bug To Reproduce
With debug:
Expected behavior Environment summary
Additional context
|
Adding the Service team to look into this issue and share the update on this. @josephkwchan, @jennyhunter-msft could you please provide an update on this once you get a chance ? Awaiting your reply. |
By the way I'm facing this issue when running: az bicep build |
I also had the same issue but I noticed there should be a fix (#20183) and my az cli was not up to date Have you tried |
Having the same issue with the latest version of azure cli. So No upgrading does not solve the issue.
|
Experiencing exactly the same issue, @navba-MSFT What is the plan for solving this issue? |
I do not use the proxy, but have the same issue when trying to run: OS: MacOS Ventura 13.5 |
Describe the bug
This is a reopening of #19420 the
az bicep install
command is once again throwing an SSL: CERTIFICATE_VERIFY_FAILED errorTo Reproduce
With debug:
Expected behavior
Bicep successfully installs.
Environment summary
Additional context
Like the pervious ticket I am also behind a corporate proxy, other commands that require the proxy certificate like
az login
are working as expected. TheREQUESTS_CA_BUNDLE
environment variable has been set to point to a file including the proxy certificate. In addition, it doesn't not appear that bicep is obeying theAZURE_CLI_DISABLE_CONNECTION_VERIFICATION
environment variable as running the following commandexport AZURE_CLI_DISABLE_CONNECTION_VERIFICATION=1
before attempting to do the install is having no effect.The text was updated successfully, but these errors were encountered: