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
There are two related problems that this issue is discussing, both highlighted in the linked issues:
How do I discover DSC Resources that aren't already on my machine?
How do I install those resources other than finding and downloading/installing them manually or with separate software depending on my platform, how the software is packaged, etc?
#92 addresses the discoverability problem by proposing a registry of DSC Resources, similar to the PowerShell Gallery.
#47 is specifically discussing a functional-within-DSC mechanism for the installation problem.
This situation is more complicated for DSCv3 than in PSDSC - in PSDSC, you could always just rely on a PowerShell repository for both discovery and install, because there was only one package type independent of platform. For DSCv3, a resource might be available through one or more package management tools and only some subset of available operating systems.
It seems unlikely that we'll write a meta resource that itself handles installing apt, yum, winget, MSI, standalone binary, and OSX packages. More likely, we'll have to do something like I proposed in #92, where resource manifests advertise how to install their associated CLI software (and any resource without the install property can only be manually installed):
Summary of the new feature / enhancement
From PS & DevOps Summit session on authoring DSCv3 modules - we will need some way to install resources.
ideally, this could even happen on demand but only from trusted sources.
@joshcorr
Proposed technical implementation details (optional)
Since each language has distinct ways to install "things", we could make "install" a capability of adapters.
dsc resource install 'computermanagementdsc' --adapter 'microsoft.dsc/powershell'
(would run install-psresource computermanagementdsc)
The text was updated successfully, but these errors were encountered: