The Bicep VS Code extension is capable of many of the features you would expect out of other language tooling. Here is a comprehensive list of the features that are currently implemented.
The bicep compiler validates that your code is authored correctly. We always validate the syntax of each file and whenever possible also validate the return types of all expressions (functions, resource bodies, parameters, outputs, etc.). Depending on the type of validation, you will see either a warning in yellow which will successfully compile with bicep build
or you will see an error in red which will fail to compile either. Bicep is more restrictive than ARM Templates, so certain behaviors in ARM Templates that you have used may not be supported and result in an error in bicep. For example, we no longer allow math functions like add()
because we support the +
operator.
See Bicep Type System for more information about Bicep data types and the type validation rules.
Bicep provides intellisense for the core language and extends to support type definitions for all resource types in Azure.
Type .
for any object to view and autocomplete its properties. Works on any param
or var
of type object
, and any resource
or module
properties (e.g. myModule.outputs.
).
Bicep knows the allowed properties and values for any resource
or module
declaration.
Easily explore all available resource types and api versions for a given type. You can type partial fragments of the type and bicep will narrow the list down accordingly.
- Keyword declarations. On an empty line you will get completions for all keywords (
param
,var
,resource
, etc.) param
andoutput
types (i.e.param myParam
)- target scopes (i.e.
targetScope =
)
Bicep has a small set of snippets for core language keywords (param
, var
, resource
, module
, output
). The snippets are contextual, so they should only show up in the places they are valid. All of the ARM Template resource snippets available in the ARM Tools VS Code extension are available as bicep resource snippets.
The bicep language service supports document symbols, which help power a broad set of code navigation features.
When your cursor is on or in a particular symbol, bicep will highlight other uses of that symbol. The color of the highlight is different for declarations of a symbol as opposed to accessing a symbol.
You can rename any symbol such as a param
or resource
and bicep will intelligently rename all the uses of that symbol
- Default keybinding is
alt
+shift
+f
on Windows,option
+shift
+f
on macOS- You can also format via the VS Code UI.
View
->Command palette...
then typeformat document
- You can also format via the VS Code UI.
- Bicep will set the following default settings for
.bicep
files when installed:
"[bicep]": {
"editor.tabSize": 2,
"editor.insertSpaces": true
}
You can change the default settings in the following places (sorted by precedence in ascending order):
- VSCode global user settings
- VSCode workspace settings
.editorconfig
files (requires EditorConfig for VSCode extension to be installed)
For small issues like misspelled symbols or incorrect casing, bicep will offer a "Quick fix" to fix it for you.
Use the "Insert Resource" command to quickly import a resource from Azure into a Bicep file.