When using bicepparam file for params, always getting error: "Error while attempting to retrieve the latest Bicep version" #30625
Labels
Auto-Assign
Auto assign by bot
Azure Deployments
az deployment/bicep/stack/deployment-scripts/ts/group export
bug
This issue requires a change to an existing behavior in the product in order to be resolved.
Configure
az configure/config
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
Possible-Solution
Service Attention
This issue is responsible by Azure service team.
Similar-Issue
Describe the bug
When I'm using the
.bicepparam
file and I want to do the deployment with Azure CLI, then I'm getting the error:Error while attempting to retrieve the latest Bicep version: HTTPSConnectionPool(host='downloads.bicep.azure.com', port=443): Max retries exceeded with url: /releases/latest (Caused by SSLError(SSLEOFError(8, '[SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurred in violation of protocol (_ssl.c:1000)'))).
The
az config set bicep.check_version=False
andaz config set bicep.use_binary_from_path=True
don't work. I'm getting still the same behavior.When I will migrate params to JSON file, works properly. Also, when I'm doing the deployment with Azure Powershell and
.bicepparam
file works well.Related command
Errors
Error while attempting to retrieve the latest Bicep version: HTTPSConnectionPool(host='downloads.bicep.azure.com', port=443): Max retries exceeded with url: /releases/latest (Caused by SSLError(SSLEOFError(8, '[SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurred in violation of protocol (_ssl.c:1000)'))).
Issue script & Debug output
Expected behavior
The command runs successfully and deploy the Bicep template without any errors. Additionally, when I enforce omiting Bicep update via
az config
then this step is omitted.Environment Summary
azure-cli 2.67.0
core 2.67.0
telemetry 1.1.0
Dependencies:
msal 1.31.0
azure-mgmt-resource 23.1.1
Python location '/opt/az/bin/python3'
Extensions directory '/home/nn-admin/.azure/cliextensions'
Additional context
Those issues looks similar/related:
The text was updated successfully, but these errors were encountered: