Download nuget via known versioning #149
Description
Most people that works with the D365 FO/SCM/Commerce stack, references to the more classic version naming scheme:
fscps/Actions/Helpers/versions.default.json
Lines 391 to 420 in da99b33
But all nuget files, has to be downloaded via the versions of the packages itself:
Get-FSCPSNuget -Version 7.0.7690.33 -Path C:\Temp\fscps.tools\10.0.45 -Type PlatformCompilerPackage
When looking at the DevOps extension - I can see that you already in some form, support the known versioning, and is able to download the nugets based on that:
Looking at the linked versions.default.json file, I made this quick hack - to be able to convert / extract between the known version and the nuget versions.
$localUri = "https://raw.githubusercontent.com/fscpscollaborative/fscps/master/Actions/Helpers/versions.default.json"
$versionObj = Invoke-RestMethod `
-Method Get `
-Uri $localUri
$versionObj | Select-PSFObject -ExcludeProperty "version" `
-Property "version as Version" `
, "Data.AppVersionGA as AppVersionGA" `
, "Data.AppVersionLatest as AppVersionLatest" `
, "Data.PlatformVersionGA as PlatformVersionGA" `
, "Data.PlatformVersionLatest as PlatformVersionLatest"
We could go 2 ways, or both. Write a cmdlet, that simply does what I just wrote. Makes it possible for people to translate from the known versioning into the details.
OR - we could get the module to run the same file, that is part of the module - with the option to pull directly from the file in the repository, but have it exposed in the Get-FSCPSNuget ala this:
Get-FSCPSNuget -KnownVersion 10.0.45 -KnownType GA -Path C:\Temp\fscps.tools\10.0.45 -Type PlatformCompilerPackage
While we are at it - I would argue that we should support the option "All", because from my perspective, I need all files. The KnownType should be GA or Hotfix, that translates into the latest / hotfix of the nugets.
I'm more than happy to take a swing at it, if you want - and feel it makes sense for your module 🤞