Azure / Azure/bicep

Intellisense for parameters (is slow to show) when constructing PS1/AzCLI commands that deploy a bicep file

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

Description

# Is your feature request related to a problem? Please describe.
When constructing `New-AzResourceGroupDeployment` commands that deploy a bicep file, I have to go back to the bicep file to reference all the parameters that I need to pass.

# Describe the solution you'd like
It would be very helpful to have the same IDE helpers that I get when writing a reference to a Bicep module (type, description, allowed values, maybe even the default value). Detection on when to show this may be a bit tricky if I'm construction the `@{}` object with the parameters and then passing it to the `New-AzResourceGroupDeployment` command, but there should be a way to indicate that manually (or some syntax in comments that could be used).

Contributor guide

Open the contributing guide

Research direction

Start by examining the existing IDE helpers for Bicep module references and how New-AzResourceGroupDeployment commands or @{} parameter objects are detected. Define how parameter type, description, allowed values, and defaults should be surfaced, including any explicit syntax for ambiguous cases; done means those helpers appear reliably when constructing deployments.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, powershell
Domain
developer-experience, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.