You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on the traces, it appears the problem is that there is recursive expression invocation happening before the Group resource is even invoked. I think the problem right now is that the intent is to allow expressions in deeply nested objects, but the engine doesn't differentiate a Group type resource from an arbitrary property object. I think the fix is for it to skip parsing expressions when the resource type is a Group.
Prerequisites
Summary
Updating the documentation for nested instances, my prior examples no longer work.
Steps to reproduce
Consider this set of minimal repro documents:
Working references/dependencies, top-level resources.
repro.working.dsc.yaml
documentResult
metadata: Microsoft.DSC: version: 3.0.0 operation: get executionType: actual startDatetime: 2025-03-13T16:26:48.071242900-05:00 endDatetime: 2025-03-13T16:26:48.950015-05:00 duration: PT0.8787721S securityContext: restricted results: - metadata: Microsoft.DSC: duration: PT0.055847S name: Deeply nested OSInfo type: Microsoft/OSInfo result: actualState: $id: https://developer.microsoft.com/json-schemas/dsc/os_info/20230303/Microsoft.Dsc.OS_Info.schema.json family: Windows version: 10.0.26100 edition: Windows 11 Enterprise bitness: '64' architecture: x86_64 - metadata: Microsoft.DSC: duration: PT0.0861504S name: Deeply nested echo type: Microsoft.DSC.Debug/Echo result: actualState: output: $id: https://developer.microsoft.com/json-schemas/dsc/os_info/20230303/Microsoft.Dsc.OS_Info.schema.json family: Windows version: 10.0.26100 edition: Windows 11 Enterprise bitness: '64' architecture: x86_64 messages: [] hadErrors: false
Failing reference, nested in a group.
repro.failing.dsc.yaml
documentdsc config get --file .\repro.failing.dsc.yaml
Result
Expected behavior
The expressions in the nested instance are deferred from the top level and processed in the
Group
resource instance.Actual behavior
It looks like DSC tries to resolve the references/resources before handing off to the group:
Error details
2025-03-13T21:31:48.344691Z ERROR Parser: Invalid resourceId or resource has not executed yet: Microsoft/OSInfo:Deeply nested OSInfo
Environment data
N/A
Version
3.0.0
Visuals
No response
The text was updated successfully, but these errors were encountered: