Skip to content
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

az bicep publish doesn't automatically install Bicep #6350

Closed
johndowns opened this issue Mar 29, 2022 · 0 comments · Fixed by Azure/azure-cli#22423
Closed

az bicep publish doesn't automatically install Bicep #6350

johndowns opened this issue Mar 29, 2022 · 0 comments · Fixed by Azure/azure-cli#22423
Assignees
Labels
bug Something isn't working
Milestone

Comments

@johndowns
Copy link
Contributor

Bicep version
run bicep --version via the Bicep CLI, az bicep version via the AZ CLI or via VS code by navigating to the extensions tab and searching for Bicep

Describe the bug
On GitHub Actions, I've noticed that if you run az bicep build without explicitly running az bicep install, the build command installs Bicep automatically.

But, if you run az bicep publish without having run az bicep install, the Azure CLI shows an error saying that Bicep isn't installed.

It'd be nice if the build and publish commands behaved consistently.

To Reproduce
Steps to reproduce the behavior:

Additional context
Add any other context about the problem here.

@ghost ghost added the Needs: Triage 🔍 label Mar 29, 2022
@alex-frankel alex-frankel added bug Something isn't working and removed Needs: Triage 🔍 labels Mar 29, 2022
@alex-frankel alex-frankel added this to the v1.0 milestone Mar 29, 2022
@stephaniezyen stephaniezyen modified the milestones: v1.0, v0.8 May 16, 2022
@shenglol shenglol modified the milestones: v0.8, v0.7 May 17, 2022
@ghost ghost locked as resolved and limited conversation to collaborators May 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

4 participants