Microsoft.PowerShell.PSResourceGet is a continuation of the PowerShellGet 3.0 undertaking. The primary preview launch of this module below the brand new identify is now out there on the PowerShell Gallery. This launch incorporates the module rename, and reintroduces assist for Azure Artifacts, GitHub packages, and Artifactory and incorporates various bug fixes.
Find out how to set up the module
To put in from PowerShellGet 3.0 previews
Set up-PSResource Microsoft.PowerShell.PSResourceGet -Prerelease
To put in from PowerShellGet 2.2.5
Set up-Module -Title Microsoft.PowerShell.PSResourceGet -AllowPrerelease
Be aware that after you put in this module you’ll need to re-register your repositories because the repository registration file has moved.
What’s included on this preview
Breaking Modifications
- PowerShellGet is now PSResourceGet
- Replace-PSScriptFile is now Replace-PSScriptFileInfo
- New-PSScriptFile is now New-PSScriptFileInfo
- Replace-ModuleManifest is now Replace-PSModuleManifest
- -Tags parameter modified to -Tag in New-PSScriptFile, Replace-PSScriptFileInfo, and Replace-ModuleManifest
- Change the kind of -InputObject from PSResourceInfo to PSResourceInfo[] for Set up-PSResource, Save-PSResource, and Uninstall-PSResource
- PSModulePath is not referenced when looking paths
New Options
- Help for Azure Artifacts, GitHub Packages, and Artifactory
Bug Fixes
- Filter out unlisted packages
- Add paging for V3 server requests
- Help for floating variations
- Replace, Save, and Set up with wildcard will get the most recent model inside specified vary
- Add positonal parameter for -Path in Publish-PSResource
- Uninstall-PSResource -WhatIf now exhibits model and path of bundle being uninstalled
- Discover returns packages from the best precedence repository solely
- Bug repair for PSCredentialInfo constructor
- Bug repair for Set up-PSResource -NoClobber parameter
- Save-PSResource now searches via all repos when no repo is specified
- Caching for improved efficiency in Uninstall-PSResource
- Bug repair for parsing bundle tags for packages that solely have .nuspec from native repository
Getting began with varied v3 feeds
Nuget Gallery
To register run Register-PSResourceRepository -Title "NuGetGallery" -Uri "https://api.nuget.org/v3/index.json"
No credentials are required for this repository.
Azure DevOps Feeds
To get the uri to your feed go to dev.azure.com > Artifacts > choose desired feed > click on “Connect with Feed” > select “NuGet.exe”. then runRegister-PSResourceRepository -Title "AdoFeedName" -Uri <My_ADO_Feed_Uri> If it’s a public feed creds arent wanted. If it’s a personal feed go to dev.azure.com > Person Settings in prime proper nook > Private Entry Tokens > Create PAT token. In your PowerShell terminal, create credential together with your username as your electronic mail account used for ADO, password can be PAT token from prior step. To make use of the credential persistence function of PSResourceGet reference the docs. You too can use with the -Credential parameter.
GitHub Packages
To register your feed run Register-PSResourceRepository -Title "GithubPackagesFeed" -Uri "https://nuget.pkg.github.com/<NAMESPACE>/index.json" The place is both the identify of your account or your group. For directions on learn how to authenticate to your GitHub packages feed reference the documentation right here. To make use of the credential persistence function of PSResourceGet reference the docs. You too can use with the -Credential parameter.
Artifactory
To register your repository run Register-PSResourceRepository -Title "JFrogFeed" -Uri "https://<myaccount>.jfrog.io/artifactory/api/nuget/v3/<myrepository>/index.json" Credentials are required for this repository, the web site UI will information you to create a PAT token. Within the pwsh terminal, create credential the place the username can be your electronic mail account used for artifactory, password can be PAT token from prior step. To make use of the credential persistence function of PSResourceGet reference the docs. You too can use with the -Credential parameter.
Versioning of this module
This primary preview of PSResourceGet is a continuation of the earlier 21 previews of PowerShellGet 3.0. We versioned this primary preview as 0.5.22-beta22. When determing this model we took into consideration semantic versioning (semver), how PowerShell does versioning, versioning patterns we had been inheriting from PowerShellGet, and learn how to greatest talk the state of the module. We wish PSResourceGet go GA with a 1.0.0 launch and comply with semver versioning from there. Within the meantime we needed to mirror that this launch is nearing RC state and is the continuation of earlier 21 previews. To perform each of those targets we comprimised on a model of 0.5.22-beta22.
Roadmap to GA
We count on this launch to ship within the subsequent preview of PowerShell 7.4. Provided that we’re transport in PowerShell 7.4 we intend to GA earlier than the GA of PowerShell 7.4 which is focused for this fall. The present plan is to have another preview launch of PSResourceGet after which launch a launch candidate (RC). From there we’ll consider readiness for GA.
Subsequent Steps for PowerShellGet
The module formally often known as CompatPowerShellGet will now ship as PowerShellGet v3. This module serves as a compatibility layer to make use of v2 syntax which calls PSResourceGet because the engine. The following preview of PowerShellGet v3 can be this compatibility layer, and take a dependency on PSResourceGet.
Find out how to give suggestions and Get Help
We can’t overstate how vital person suggestions is at this stage within the growth of the module. Suggestions from preview releases assist inform design choices with out incurring a breaking change as soon as usually out there and utilized in manufacturing.
With the intention to assist us to make key choices across the conduct of the module please give us suggestions by opening points in our GitHub repository.
Sydney
PowerShell Crew
