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
{{ message }}
Repository navigation
differingProperties always propagated on adapter resource #849
This requires the adapter to synthetically invoke the get operation for the resource, but that should make everything more functional for users.
I believe this is also related to #267, which proposes a model for simplifying the implementation of adapters so that they are able to return data to DSC with minimal munging. The PSDSC adapters would still need to invoke both the Test() and Get() operations for classic PSDSC resources to return the appropriate JSON, but this could simplify the overall implementation and enable simpler implementations for new adapters, too.
Activity
michaeltlombardi commentedon May 30, 2025
I think a major component of this is that the adapter doesn't fully munge the PSDSC resource output to match DSC expectations.
I think the implementation should take this resource output:
{ "inDesiredState": true }And return it from the adapter as
{"_inDesiredState":true,"Name":"spooler","StartupType":"Automatic"}This requires the adapter to synthetically invoke the
getoperation for the resource, but that should make everything more functional for users.I believe this is also related to #267, which proposes a model for simplifying the implementation of adapters so that they are able to return data to DSC with minimal munging. The PSDSC adapters would still need to invoke both the
Test()andGet()operations for classic PSDSC resources to return the appropriate JSON, but this could simplify the overall implementation and enable simpler implementations for new adapters, too.