Changed

• Update apiVersions in all snippets
• Build maintenance and security work

Added

• Add *Cidr functions to completions #1690

Fixed

• Update schemas cache to state as of April 23, 2024 (updating past that point is currently blocked by #1733)
• Fix current return values of tenant() for completions #1701
• Update some snippets to pass Armory checks #1721
  • Ubuntu Virtual Machine
  • Virtual Network
  • Windows Virtual Machine
• Fix issue when using the Remote Repositories extension #1647

New Contributors

• @AbhitejJohn made their first contribution in https://github.com/microsoft/vscode-azurearmtools/pull/1703

Full Changelog: https://github.com/microsoft/vscode-azurearmtools/compare/v0.15.11...v0.15.12

Changed

• Update schemas cache
• Update dependencies
• Make it easier to ship schema cache updates in the future
• Update to dotnet 7.0
• Update apiVersions in snippets

Attempting to solve installation issue

Version 0.15.8 (2022-10-03)

Changed

• Updated schemas cache

Changed

• Update schemas cache
• Update dependencies

Added

• Automanage snippets (thanks Andrew Smith!) #1508:
  • Automanage Best Practices DevTest Assignment
  • Automanage Best Practices Prod Assignment
  • Automanage Custom Profile Assignment
  • Automanage Create Custom Profile
• Add join() function and update a few function descriptions #1517

Version 0.15.7 (2022-05-11)

Fixed

• Update schemas cache (fixes part of Warning about apiVersion (ot yet added in 2019-04-01/deploymentTemplate.json
• Update dependencies

Added

• New ARM functions: dateTimeFromEpoch, dateTimeToEpoch #1462
• Add Collapse All to JSON Outline #1472

Full changelog: https://github.com/microsoft/vscode-azurearmtools/compare/v0.15.6...v0.15.7

Fixed

• Update schemas cache
• Upgrade to .NET 6 to support Mac M1/Arm640
• Engineering/test improvements

Full Changelog: https://github.com/microsoft/vscode-azurearmtools/compare/v0.15.5...v0.15.6

Version 0.15.5 (2021-11-15)

Due to technical issues originating with a recent change in Azure schemas, we haven't been able to update our schemas for a while. This release fixes that issue.

Added

• Service bus and blob container snippets #1379
• Add definitions for items(), tenant() and managementGroup() functions #1397

Fixed

• Add support to pick up schemas again (due to breaking change in schemas) #1324
• Microsoft.Web/sites out of date #1396
• Microsoft.Authorization/policyAssignments latest API unavailable. #1384
• Microsoft.Authorization/roleAssignments is unrecognized #1366
• Microsoft.Web/hostingEnvironments most apiVersions not recognized #1344

Fixed

• Using scaffolding snippets in empty JSON file should not require CTRL+SPACE #1390

Added

• Added notification message about availability of Bicep extension (can choose to never see again) #1304

Updated

• Updated snippet apiVersion values #1357, #1373

Fixed

• ARM tools snippet completions show up in bicepconfig.json files #1307
• Note in "providers" template function description that it has been deprecated #1356

Engineering

• Updated to TypeScript 4
• Test improvements
• Improvements to error telemetry from language server
• Moved reource snippets to individual template files to make editing and proofing easier #1370

Updated

• Updated schemas
• Updated function metadata #1311

Fixed

• Correct minor typo for deprecrated (thanks Jack Blower @ElvenSpellmaker!) #1301

Added

• Added icons for loadbalancer, virtual machine scaleset, and service fabric resources (thanks Jason Gilbertson @jagilber!) #1255
• Understand new top-level "scope" property #967

Fixed

• Find references for a nested template parameter incorrectly finds matches in the parameter file #1269
• Show apiVersions in reverse chronological order #1279
• Clicking F12 while on a parameter definition should show all refs but instead says "no definition found" #1267

Maintenance

• Telemetry to better understand which resource types and apiVersions do not have schemas #1250
• Retrieve list of valid schemas and apiVersions from the language server for future features #1258

Linked file support

Version 0.15.0 (2021-03-08)

Added

• Support for linked templates validation and parameter completion
  • templateLink.relativePath (requires apiVersion 2020-06-01 or higher of Microsoft.Resources/deployments for template specs, 2020-10-01 for direct deployment)
  • templateLink.uri
  • deployment().properties.templateLink.uri
  • See README.md for more information
  • "parametersLink" is not supported (but "parameters" is)
  • Experiences include:
    • Validation of linked templates using the value of parameter values supplied to the template
    • Parameter validation (missing, extra, type mismatch)
    • "Light-bulb" and snippet support to fill in parameter values for a linked template
    • CTRL-click on relativePath value or click on code lens to navigate to linked template
    • Can navigate to URI-based linked templates
  • Requires full template validation to be enabled (either all top-level parameters have a default value or else a parameter file is selected)
• Enable full template validation if all top-level parameters have default values, even if no parameter file has been specified #1217
• Show warning notification when the azureResourceManagerTools.languageServer.dotnetExePath setting is in use #1181, #1180
• Schemas updated

Fixed

• Clearer notification when the extension is starting up and loading schemas #463
• Intellisense for AutoScaleSettings recommends "statistics" when it should be "statistic" #1141
• Incorrect validation errors in user-defined functions when using recently added builtin functions (createObject etc.) #1153

Added from alpha2:

Mostly bug fixes and experience improvements.

Added

• How to install:
  • In VS Code, F1 -> "Extensions: Install from VSIX..." -> browse to VSIX and select -> restart VS Code
    How to uninstall:
  • In VS Code, View Extensions -> Find "Azure Resource Manager (ARM) Tools" extension -> click on tools icon -> Install Another Version...
  • Or wait until the official 0.15.0 release is published, it should automatically upgrade from the alpha
• Support for validation of linked templates
  • Scenarios supported:
    • Relative path (requires apiVersion 2020-10-01 or higher of Microsoft.Resources/deployments), e.g.:

        {
            "name": "linkedDeployment1",
            "type": "Microsoft.Resources/deployments",
            "apiVersion": "2020-10-01",
            "properties": {
                "mode": "Incremental",
                "templateLink": {
                    // Relative to current template's folder
                    "relativePath": "child.json"
                },
                "parameters": {
                }
            }
        }

- Full URI, e.g.:

        {
            "name": "linkedDeployment1",
            "type": "Microsoft.Resources/deployments",
            "apiVersion": "2020-10-01",
            "properties": {
                "mode": "Incremental",
                "templateLink": {
                    "uri": "https://raw.githubusercontent.com/StephenWeatherford/template-examples/master/linkedTemplates/uri/child.json"
                },
                "parameters": {
                }
            }
        }

- Relative to deployed template location

        {
            "name": "linkedDeployment1",
            "type": "Microsoft.Resources/deployments",
            "apiVersion": "2020-10-01",
            "properties": {
                "mode": "Incremental",
                "templateLink": {
                    // When the template is deployed, this will be relative to the deployed location
                    // While editing, this will be relative to the current template's local file folder
                    "uri": "[uri(deployment().properties.templateLink.uri, 'child.json')]"
                },
                "parameters": {
                }
            }
        }

• Linked template support requires either that all top-level parameters have a value, so either
  • All top-level parameter definitions has a default value
  • Or a parameter file is associated with the template
• "parametersLink" is not supported (but "parameters" is)
• Known Issues:
  • Schema for Microsoft.Resources/deployments@2020-10-01 is required to successfully deploy to Azure with
    relativePath, but its schema hasn't been published yet, causing false warnings and degradation of Intellisense.
    Work-around is to use version 2020-06-01 for editing and switch back to 2020-10-01 before deploying.
• Examples of experiences supported:
  • Validation of linked templates up to one level
  • Parameter validation
  • "Light-bulb" and snippet support to fill in parameter values for a linked template
  • CTRL-click on relativePath value or click on code lens to navigate to linked template
• Enter bugs/issues/suggestions: Easiest is to submit them in our repo

Fixed

• Clear notification when the extension is starting up and loading schemas

Added from alpha1:

• templateLink.uri support
• Full validation is enabled even without a parameter file if all parameters have default values

Added

• Support for validation of linked templates
  • How to install:
    • In VS Code, F1 -> "Extensions: Install from VSIX..." -> browse to VSIX and select -> restart VS Code
      How to uninstall:
    • In VS Code, View Extensions -> Find "Azure Resource Manager (ARM) Tools" extension -> click on tools icon -> Install Another Version...
    • Or wait until the official 0.15.0 release is published, it should automatically upgrade from the alpha
  • Scenarios supported:
    • Relative path (requires apiVersion 2020-10-01 or higher of Microsoft.Resources/deployments), e.g.:

        {
            "name": "linkedDeployment1",
            "type": "Microsoft.Resources/deployments",
            "apiVersion": "2020-10-01",
            "properties": {
                "mode": "Incremental",
                "templateLink": {
                    // Relative to current template's folder
                    "relativePath": "child.json"
                },
                "parameters": {
                }
            }
        }

- Full URI, e.g.:

        {
            "name": "linkedDeployment1",
            "type": "Microsoft.Resources/deployments",
            "apiVersion": "2020-10-01",
            "properties": {
                "mode": "Incremental",
                "templateLink": {
                    "uri": "https://raw.githubusercontent.com/StephenWeatherford/template-examples/master/linkedTemplates/uri/child.json"
                },
                "parameters": {
                }
            }
        }

- Relative to deployed template location

        {
            "name": "linkedDeployment1",
            "type": "Microsoft.Resources/deployments",
            "apiVersion": "2020-10-01",
            "properties": {
                "mode": "Incremental",
                "templateLink": {
                    // When the template is deployed, this will be relative to the deployed location
                    // While editing, this will be relative to the current template's local file folder
                    "uri": "[uri(deployment().properties.templateLink.uri, 'child.json')]"
                },
                "parameters": {
                }
            }
        }

• Linked template support requires either that all top-level parameters have a value, so either
  • All top-level parameter definitions has a default value
  • Or a parameter file is associated with the template
• "parametersLink" is not supported (but "parameters" is)
• Known Issues:
  • Schema for Microsoft.Resources/deployments@2020-10-01 is required to successfully deploy to Azure with
    relativePath, but its schema hasn't been published yet, causing false warnings and degradation of Intellisense.
    Work-around is to use version 2020-06-01 for editing and switch back to 2020-10-01 before deploying.
• Examples of experiences supported:
  • Validation of linked templates up to one level
  • Parameter validation
  • "Light-bulb" and snippet support to fill in parameter values for a linked template
  • CTRL-click on relativePath value or click on code lens to navigate to linked template
• Enter bugs/issues/suggestions: Easiest is to submit them in our repo

Fixed

• Clear notification when the extension is starting up and loading schemas

Added

• Support for validation of linked templates (alpha) - only "relativePath" in templateLink is supported in this version - "uri" support expected soon
  • How to install:
    • In VS Code, F1 -> "Extensions: Install from VSIX..." -> browse to VSIX and select -> restart VS Code
      How to uninstall:
    • In VS Code, View Extensions -> Find "Azure Resource Manager (ARM) Tools" extension -> click on tools icon -> Install Another Version...
    • Or wait until the official 0.15.0 release is published, it should automatically upgrade from the alpha
  • "parametersLink" is not supported (but "parameters" is)
  • Examples of experiences supported:
    • Validation of linked templates up to one level
    • Parameter validation
    • "Light-bulb" and snippet support to fill in parameter values for a linked template
    • CTRL-click on relativePath value or click on code lens to navigate to linked template
  • Enter bugs/issues/suggestions in our repo

Fixed

• Clear notification when the extension is starting up and loading schemas

Fixed

• Give warning if the wrong schema might be wrong for the deployment resources being used #1055
• Add support for pickZones() function (thanks Brian Golden @bgold09!) #1130
• Add mention of ARM Viewer to README #1140
• Upgrade Microsoft.Resources/deployments apiVersion to support relativePath property #1137
• Update schemas cache
• Split nested snippet into inner/outer #1157

Added

• New Feature: Extract to variable/parameter [#515] (https://github.com/microsoft/vscode-azurearmtools/issues/515)
  • Thanks to Nils Hedström @nilshedstrom for implementing this new feature!
• Hover over an expression or a multi-line string to see a easy-to-read, formatted version of it #1092

Fixed

• createArray() now supports creating an empty array, update tooling to avoid false positive #1050
• Extension causes high cpu load with large numbers of variables/parameters/resources #1051
• We should support getting references from the entire 'variables('xxx')' or params expression, not just inside 'xxx' #1046
• Stop displaying our own error message at the same time as .net extension #1093
• Validation error with resourceGroup() tags when using parameter file #831
• dateTimeAdd() in certain scenarios gives a template validation error #1056
• Validation of template function "deployment" #1060

Contains performance fixes for large numbers of parameters/variables, plus preview of extract var/params.

Added

• Completions for dependsOn array elements
• Intellisense improvements:
  • Fixed:
    • Completions cause entire current word to be deleted #903
    • Tab completion of params/vars wipes out remainder of string #349
    • Sparse filtering does not work for our expression Intellisense #572
• Child/parent code lenses for resources

Changed

• If we find just a single matching parameter file, we now automatically use it without asking. It can be manually disassociated or associated with a different parameter file, and this behavior can be turned off via VS Code settings #911
• ARM Template Outline view and Intellisense now use a more compact format for the name and type of resources that are expressions, based on the new string interpolation format for Bicep
• ARM Template Outline view now shows only the last segment of a resource's name
• ARM Template Outline view now also shows the last segment of a resource's type
• For a cleaner look, parameter code lenses just show "Using default value" for parameters with default values, and do not actually repeat the default value #999

Fixed

• Missing one warning in the error list after changing the property from "inner" to "outer" #891
• Added location property to deployment() function metadata #936
• "Cannot read property 'start' of undefined: TypeError: Cannot read property 'start' of undefined" in suites #858
• List function is not recognized #949
• Support for new template functions: createObject(), false(), true(), null()
• resourceId completion should pull from within the correct scope of resources #775
• Unable to remove file reference from parameter file to template file if template file is deleted #952
• Using schema with http instead of https sets language to arm-template but schema Intellisense/validation don't work #834