You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bicep version Bicep CLI version 0.3.1 (d0f5c9b164)
Describe the bug
When following the tutorial, the New-AzResourceGroupDeployment command could produce an error using the provided Bicep files.
The 'name' parameter in the mentioned PowerShell example only specifies the deployment name but do not overwrite the storage account name parameter in the Bicep file.
The phrase 'name' for that parameter seems a little bit unlucky in this case.
For someone who is exactly following the tutorial this could be a little bit confusing.
To Reproduce
Deploying the Bicep file '01.bicep' using the command from the screenshot below.
Providing any name using the '-name' parameter.
See the provided name only affects the deployment name and not the actual storage account name.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Bicep version
Bicep CLI version 0.3.1 (d0f5c9b164)
Describe the bug
When following the tutorial, the New-AzResourceGroupDeployment command could produce an error using the provided Bicep files.
The 'name' parameter in the mentioned PowerShell example only specifies the deployment name but do not overwrite the storage account name parameter in the Bicep file.
The phrase 'name' for that parameter seems a little bit unlucky in this case.
For someone who is exactly following the tutorial this could be a little bit confusing.
To Reproduce
Deploying the Bicep file '01.bicep' using the command from the screenshot below.
Providing any name using the '-name' parameter.
See the provided name only affects the deployment name and not the actual storage account name.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: