Install PowerShell7 resource about dsc

[SteveL-MSFT]

Was thinking about this and if this resource ships with DSC, then the individual packages (Windows, Linux, macOS) would have their own versions so we don't need to dynamically choose and ship all OS support to every OS. Basically the choice would be in our build process dependent on the host OS.

I think we want channel support (stable, preview, and LTS) but always the latest and probably not support specific version (we can revisit in the future). Initial scenario is for bootstrapping a VM, so we can defer scope (currentUser, allUsers) later.

[michaeltlombardi]

I would prefer that DSC not try to handle multi-platform behavior from the manifest, both because is can lead to substantially more complicated manifests and edge case errors, and because I think the better practice and pattern is to use a small executable to select the correct shell script.

Should this resource handle versions, or just always grab the latest stable release? Are there other considerations to account for in the install, like path, or should it just use the defaults?

[kilasuit]

Could this not make use of the install-powershell scripts in the PowerShell repo?

[SteveL-MSFT]

Could this not make use of the install-powershell scripts in the PowerShell repo?

Those scripts were designed for our CI system when PS7 wasn't readily available so not ever intended to be used outside of that environment. At this time, it's probably easier to write the resource from scratch to be honest.

[anmenaga]

Looks like Microsoft.WinGet.DSC/WinGetPackage does this:

    - name: PowerShell 7 Preview
      type: Microsoft.WinGet.DSC/WinGetPackage
      properties:
        Id: Microsoft.PowerShell.Preview