Add DSC scope support to ScopeHelper resource ID formatting

[Gijsreyn]

Description

Adds support for DSC scope to Bicep resource ID formatting. DSC resources don't use traditional ARM resource IDS, so the implementation uses a custom concatenation format.

Example Usage

Tested this change with a local file reported in issue #17670. Bicep file:

targetScope = 'desiredStateConfiguration'

// use workaround where Bicep currently requires version in date format
resource echo 'Microsoft.DSC.Debug/Echo@2025-01-01' = {
  name: 'exampleEcho'
  properties: {
    output: 'Hello, world!'
  }
}

output exampleOutput string = echo.properties.output

Returns:

{
  "$schema": "https://aka.ms/dsc/schemas/v3/bundled/config/document.json",
  "contentVersion": "1.0.0.0",
  "metadata": {
    "_generator": {
      "name": "bicep",
      "version": "0.37.52.64608",
      "templateHash": "928342520835393415"
    }
  },
  "resources": [
    {
      "type": "Microsoft.DSC.Debug/Echo",
      "apiVersion": "2025-01-01",
      "name": "exampleEcho",
      "properties": {
        "output": "Hello, world!"
      }
    }
  ],
  "outputs": {
    "exampleOutput": {
      "type": "string",
      "value": "[reference(concat('Microsoft.DSC.Debug/Echo', '/', 'exampleEcho'), '2025-01-01').output]"
    }
  }
}

Checklist

• I have read and adhere to the contribution guide.

Microsoft Reviewers: Open in CodeFlow

[Gijsreyn]

Hey @anthony-c-martin or @andyleejordan, is this perhaps something you can look at? It's currently a blocker on the DSC side. Much appreciated!

[andyleejordan]

Hi @Gijsreyn, trust me, I would love to get back to this work. Unfortunately, more pressing things have filled my plate. Hopefully we'll get to it soon enough.

[SteveL-MSFT]

This will change with this PR PowerShell/DSC#1188