Feature Req: Exchange data between resources
Currently, all data needed for a resource to work must be available at MOF compile time. If a resource depends on information which was not available at compile time we have to add logic to our resources to search for this information.
Example:
We have a resource which handles a certificate enrollment and another to bind the thumbprint to a web-binding. As we don't know the thumbprint up front, we have to add logic to the web-binding resource to have it search for, e.g. a friendly name or another attribute which was settable by the enrollment resource.
Feature Req: It would be great if we could subscribe to result output of a resource. We could for example bind to NotConfigurable dsc property.
This would allow for a more dynamic approach without the need to customize resource internals.
Example pseudo:
configuration PSEUDO {
EnrollCert WebXSSL {
EnrollMentService = '<a rel="nofollow noreferrer" href="https://enroll.me'">https://enroll.me'</a>;
Certtype = 'ServerAuth'
}
WebBinding WebXSSL {
Name = X
ThumbPrint = '[EnrollCert]WebXSSL.ThumbPrint'
}
}
In this case, the enrollcert resource would have a NotConfigurable DSC property for thumbprint
Ben Gelens
shared this idea
Thanks Ben for opening this issue, but looks like Jason beat you :)
https://windowsserver.uservoice.com/forums/301869-powershell/suggestions/13399734-returning-information-from-dsc-resource-to-another
Please add your scenario and upvote the one Jason opened.