Azure / Azure/bicep

Update VS Code Ext landing page text to specify to manually install Bicep Cli

Open
#11,214 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Bicep
Stars
3.6k
Forks
830
Avg merge
1d 21m
Merged PRs (30d)
79

Description

We have the following Text and Link on the `details` page for the VSCode Bicep extension.
- That "Bicep VS Code Extension" link already points to the setup page
- https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/install#vs-code-and-bicep-extension

![image](https://github.com/Azure/bicep/assets/3605266/1ccf8fcb-34a2-48f9-8e06-e8bc8cf75f81)

We had some other issues where an Azure PowerShell user did not have the Bicep cli installed.

We document below that Bicep cli is a manual install in these circumstances.

#### Below are the scenarios that we want to cover for new users to point them to the right place and info to install Bicep cli:
![image](https://github.com/Azure/bicep/assets/3605266/cf999534-3b82-4498-8a14-5e2e5028b36b)

---

### TODO: Update Text description on VS Code Landing page:
- Make **more prominent message and link** to the setup page, so that users should visit the docs page to learn how to manually install the Bicep Cli.

Contributor guide

Open the contributing guide

Research direction

Start at the VS Code Bicep extension's details or landing page and review the existing "Bicep VS Code Extension" link to the documented setup page. Update the landing-page text so the setup link and the need to manually install the Bicep CLI are more prominent, then verify that the scenarios in the issue are clearly covered.

Written by the indexing model from the issue text.

Assessment

Tech stack
vscode
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.