${WinGetConfigRoot} in DSCv3 configuration

[Jonas Feller (J0F3)]

Hi

I created a winget configuration from my existing installation using winget configure export --all -o myconfig.dsc.winget which creates apparently a dscv3 based configuration now (which I actually like):

# Created using winget configure export 1.11.430
# yaml-language-server: $schema=https://aka.ms/configuration-dsc-schema/0.3
$schema: https://raw.githubusercontent.com/PowerShell/DSC/main/schemas/2023/08/config/document.json
metadata:
  winget:
    processor:
      identifier: 'dscv3'
resources:
  - name: Microsoft.WinGet/Package_qvqwdsn2
    type: Microsoft.WinGet/Package
    metadata:
      description: 'Install/ Configure Microsoft PowerShell (7)'
    properties:
      id: 'Microsoft.PowerShell'
      source: 'winget'
  - name: Microsoft.DSC.Transitional/RunCommandOnSet_t5cmk5sw
    type: Microsoft.DSC.Transitional/RunCommandOnSet
    metadata:
      description: 'Install Microsoft.Windows.Settings module'
    dependsOn:
      - Microsoft.WinGet/Package_qvqwdsn2
    properties:
      arguments:
        - '-NoProfile'
        - '-NoLogo'
        - '-Command'
        - 'if (-not (Get-Module -ListAvailable -Name Microsoft.Windows.Settings)) { Install-Module
          -Name Microsoft.Windows.Settings -Confirm:$False -Force -AllowPrerelease -AllowClobber
          }'
      executable: 'pwsh'
  - name: Microsoft.Windows.
 ....
...

I tried then to expand the configuration to run a simple PowerShell script like so:

  - name: Microsoft.DSC.Transitional/RunCommandOnSet_myscript
    type: Microsoft.DSC.Transitional/RunCommandOnSet
    metadata:
      description: 'run config script'
    properties:
      arguments:
        - '-NoProfile'
        - '-NoLogo'
        - '-Command'
        - '${WinGetConfigRoot}\configure.ps1'
      executable: 'powershell'

But this did not work because ${WinGetConfigRoot} seems not be expanded and so the script was not found. When I specify the full path to the script then it works as expected.

So, is that a known issue for for DSCv3 based configurations for now or should ${WinGetConfigRoot} also with this DSCv3 based configuration (which is still very early preview as far I understand)?

Thanks!