Still struggling with Datum Handlers and variables in mof files

[gabeKay]

Hi again,

im still struggling with Datum Handlers and variables

The Datum module correctly processes variable substitution in the RSOP YAML output (e.g., [x={ $Node.NodeName}=] is correctly resolved to the actual node name), but fails to perform the same substitution when generating MOF files. While the DatumHandler successfully processes these variables during RSOP generation through ConvertTo-Datum, the same variables remain unresolved in the MOF generation process, resulting in literal strings instead of the resolved values in the final MOF files.

I tried a lot but its not eneugh.

Thanks for your help :)

gabeKay

[raandree]

That is weird as the MOF files are generated from the RSOP data. We are getting the rsop data in CompileRootConfiguration.ps1 by calling Get-DatumRsopCache.

What do you get when calling Get-DatumRsopCache after the build finished? Do you get the data you expect or have the scriptblocks not resolved?

[gabeKay]

I actually built a Frankenstein :) The Infra Sample is too simple for my requirements, and the DSC Workshop is too much. So I broke everything down and overlooked the SamplerPipeline. I now need to integrate the CompileRootMeta or implement the DatumCache directly into the Root.

What you built is really complex but very good. However, I never found a proper guide. But I learned a lot from it :)

So basically, the ticket is done, as the issue is on my side. I just need to find time to implement it. During my research, I never came across the SamplerPipeline, crazy.

[raandree]

The 'Infra Sample' is also pretty outdated. It was the DscWorkshop's predecessor.

Using the DscWorkshop as it is shouldn't be too much and too complex. It works out of the box and creates all required artifacts for all possible scenarios and the Common Tasks Library is a good start for most standard scenarios.

Maybe you can save yourself some time by implementing the DscWorkshop instead of tearing it apart.