Highlights
Bicep Team:
- [Bicep CLI ONLY] Enable supplemental params validation with
build-params
command (#11975)- Use cases for supplemental params can be found here.
- Bicep CLI support only, Az CLI/Powershell support is coming soon.
- Deprecating
validate-params
command PR (#11974)- We will now be validating inline params through the build-params command
- Compile-time variable imports (#11657)
- Allow bicepparam files to reference Registry Modules (including BR, TS & JSON paths) (#11703)
- [EXPERIMENTAL] F12 Bicep Publish with Sources Part 1 (#11896)
- Must use temporary feature flag: "publishSource"
Features and Bug Fixes
Bicep Team:
- Deploy Pane: Support tenant & management group scope deployments (#11917)
- Add linter rule to recommend using modules instead of 'Microsoft.Resources/deployments' resources (#11848)
- Reword experimental feature usage error message (#11961)
- Decompile Bicepparams: Use consistent URI -> FS conversion (#11834)
- Use languageVersion 2.0 if any types are imported (#11886)
- Add implicit nullability to optional module params (#11887)
- Block calls to scope functions in
.bicepparam
files (#11903) - Block nested deployment resources with inner scoped evaluation and symbolic references to outer scope (#11884)
- Support variable imports in .bicepparam files (#11879)
- Fix nested type property decorator completions (#11972)
- Perform deep validation on assigned parameter values in
.bicepparam
files (#11985) - Added Bicep AvailableItemName to MSBuild props (#11915)
- Added support for skipping bicep build in MSBuild targets (#11916)
- Fix compiled representation of wildcard variable property references (#12048)
- Provide a declared type for imported variable accesses to enable completions (#12050)