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
This is parity with invoke-dscresource, correct? In native command, what is the best option for input of property:value pairs? Do we still input a hashtable?
@mgreenegit I would expect this to work like dsc resource (get|set|test) -r <command_resource> - you pass a JSON blob over stdin with the property bag.
In a super fancy ideal world that I think is explicitly out of scope for now, it would be very neat if DSC could lookup the resource specified by -r <name> and dynamically provide CLI flags for the properties. But for now, I think JSON over stdin is the sensible option and doesn't require any new engineering.
This would also mean you could do something like:
@{
Scope='Machine'Ensure='Present'UpdateAutomatically=$trueUpdateFrequency=45
} |ConvertTo-Json| dsc resource get -r TSToy.Example/PSTSToy
Summary of the new feature / enhancement
Enable
dsc resource get -r <psresource>
to invokeget
,set
, andtest
to a PS resourceProposed technical implementation details (optional)
No response
The text was updated successfully, but these errors were encountered: