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

[asdkant-bf]

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).

[brwilkinson]

Hi @asdkant-bf

Can you please assist us to understand the problem? Does below cover your ask, or was there something more?

For Powershell we do have the following auto complete on dynamic parameters. Notice storage and location come from the main. Bicep template. Notice these do come at the end of the normal parameters.

Powershell 7 also supports a Splatting feature, if you create the @param variable first, then you can auto complete inside of the hash table above, used for the splatting.

The main issue right now, is that this is extremely slow. This is likely something that we can track or look into improving, if there was some requests for this.

[asdkant-bf]

@brwilkinson Yes, that sounds like what I want, but I haven't seen it working on my machine. How do I enable this?

[brwilkinson]

@asdkant-bf a few questions:

• what operating system do you have?
• What version of powershell do you use?
  • $psversiontable
• What editor do you deploy your Bicep from?
• What bicep version do you have?
  • bicep --version
• if you use vscode, is the script file set to powershell and do you have the 'vscode Powershell extension' installed in vscode?

It's recommended to use powershell 7, which is the Core edition.

https://learn.microsoft.com/en-us/powershell/scripting/install/installing-powershell-on-windows?view=powershell-7.3#install-powershell-using-winget-recommended

https://learn.microsoft.com/en-us/powershell/scripting/dev-cross-plat/vscode/using-vscode?view=powershell-7.3#choosing-a-version-of-powershell-to-use-with-the-extension

[brwilkinson]

something that came to mind:

• intellisense might not work, if you are using a $variable in the path to your template e.g. $base\template.bicep
  • you could set the location to that directory or map a psdrive if you want to have a shorter path to the template file.

[brwilkinson]

It appears that the request here is a standard configuration and should just work.

• if not resolved can troubleshoot locally, however this can likely be closed? @asdkant-bf are you able to confirm?