Enable PowerShell module auto-discovery in DSC
I recently discovered that in my DSC resource I can't call a powershell cmdlet that internally calls into another powershell cmdlet - that fails because DSC doesn’t explicitly import the full powershell module, but only imports specific .psm1 files.
Note, same (cmdlet calling another cmdlet) works perfectly fine when executed from Powershell cmd prompt. Let's fix it for DSC.
Thank you for your feedback!
Based on its current ranking compared to other feedback items and product schedule, work on this item is pending (and will be driven by) further customer input. If you did not open this issue and are also impacted by it, please vote this item up.