How to access parameters from within command schema?

[aaroncorgan]

Im using a powershell script to generate a manifest resource command schema. problem is, $input is null when i try to build the schema using the same 'args' as all of the rest of my manifest. If $input isnt available for generating schema via command, how else can I access those parameters? "[parameters('foo')]" doesnt work, $input doesnt work, $env:foo doesnt work, is there just no way to accomplish this particular goal? was hoping to avoid having to step outside of the dsc runtime to gather info but not sure I have much choice.

these are the args used for all my commands in the resource manifest:

"args": [
      "-NoLogo",
      "-NonInteractive",
      "-NoProfile",
      "-ExecutionPolicy",
      "Bypass",
      "-Command",
      "$Input | <script.ps1> <operation>"

[aaroncorgan]

using get-content worked perfectly!

[Gijsreyn]

Hey @aaroncorgan, I was trying to understand your issue, but couldn't grasp the full. Could you mind posting in step-by-step what you tried to achieve :)?

[aaroncorgan]

DSC v3 custom resource, in the manifest for my various operation commands, im using stdin to pass an input parameter from my configuration file, thats defined in the resource instance. using this args value for each operation within my resource manifest:

"args": [
      "-NoLogo",
      "-NonInteractive",
      "-NoProfile",
      "-ExecutionPolicy",
      "Bypass",
      "-Command",
      "$Input | <script.ps1> <operation>"

im also using a command schema, which i have configured as just another operation in the powershell script im using for all my other operations (ie, get, set, test, and schema). I had build my internal functions around the resource instance parameters always existing, and it was a pain that command schemas werent being fed them via stdin like the operations were. For my setup, i was essentially just treating the command schema as an operation along side the others, so i was wondering if it not passing in the parameters via stdin was intentional or if I was just doing something wrong/using the wrong syntax. Im currently using get-content to pull the values directly from my config file but its less than ideal, id honestly love if I could just throw a "acceptsStdin": true property onto the command schema object, and then just utilize the same args value structure as the rest of my operation objects (and internally would vastly simplify how im having to structure things).

Otherwise, ive been loving dsc v3 so far and its been a fun interesting challenge to implement custom resources. Im sure the documentation and examples and such will get fleshed out over time because really thats my only complaint! (other than all the bugs preventing yaml from being usable but i see thats already been acknowledged in an issue so its nbd to use json for now). Thanks again!

[Gijsreyn]

Mhm interesting... If you want to have it in, you can always open an issue, and this suggestion :). Thanks for the share