Cannot get either Powershell adapter working

[hansze]

I have tried using both the Powershell.DSC adapter for class based PowerShell resources as well as WindowsPowerShell.Dsc classic (Binary / File - is this supported) resources to no avail.

The behavior I get for both is that they fail in the resource discovery phase but strangely enough differently. Both get hung up and 'never' return a config get operation. I tried both JSON and YAML input via file.

Below my failed attempts with simple samples using the script based with resources define in the below JSON and calling

dsc -l trace config get -p <PathToJSONFIle>

JSON

{
    "$schema":  "https://raw.githubusercontent.com/PowerShell/DSC/main/schemas/2024/04/config/document.json",
    "resources":  [
        {
            "name":  "SimpleClassicFileResourceTest",
            "type":  "Microsoft.Windows/WindowsPowerShell",
            "properties":  {
                "resources":  [
                    {
                        "name":  "TestFile",
                        "type":  "PSDesiredStateConfiguration/File",
                        "properties":  {
                            "DestinationPath":  "C:\\PSTEMP\\Test.txt",
                            "type": "File",
                            "contents": "Nothing special"
                            "Ensure": "Present"
                        }
                    }
                ]

            }
        }
    ]
}

Hangs... stopped at 25min

I am not sure why it is even trying to enumerate all these resources as if it was doing a list all - the config is very specifically looking for an adapter type Microsoft.Windows/WindowsPowerShell with fully qualified name PSDesiredStateConfiguration/File. As mentioned above this is implemented as binary but that should not matter... or. The behavior does not indicate that this is the issue as it never even gets back from enumerating the PowerShell.Dsc adapted resources.

Below the second adapter failed attempt. Here it can be seen at least enumerating the proper adapter type straight away but is still hangs...

YAML

resources:
- name: SimpleClassBased
  type: Microsoft.DSC/PowerShell
  properties:
    resources:
    - name: TestEnv
      type: PSDscResources/Environment
      properties:
        Name: TestEnv
        Ensure: Present
        Value: TestValue

Same command as previously but ´slightly different path

dsc.exe config get -p

Goes for the proper adapter right away

Even loads the YAML and finds the adapted resource PSDscResources/Environment

But then hangsup (just waited 3 + min here...)

Before I try to debug this stepping in code... can anyone verify that what I have attempted above should work and is intended to work this way. There were no docs that I could find showing how to leverage adapted resources.

Version: dsc 3.0.0-preview.8

[hansze]

Seems to be related to Module conflicts on my test machine - I need to do better house-cleaning. Spun up new test VM and tests above succeed now. Lesson learned.