Open ThomasNieto opened 1 year ago
The long-term alternative to this (that I think is more idiomatic, because the implementation of Reasons inherently conflates Get
and Test
) is to add support for reporting how a DSC Resource is out-of-state via the Test method.
In the short-term, I've been updating the documentation^1 to recommend any module implementing Reasons use the module's name as a prefix in the class name.
Prerequisites
Steps to reproduce
PSDSC should ship a
Reasons
class so each DSC resource module doesn't need to define it. It would also address the issue withReasons
type name conflict issues. Backstory: https://github.com/AnyPackage/AnyPackageDsc/issues/12Expected behavior
Actual behavior
Error details
No response
Environment data
Version
2.0.6
Visuals
No response