PowerShellGet is a PowerShell module with commands for discovering, installing, updating and publishing the PowerShell artifacts like Modules, Scripts, and DSC Resources. PowerShellGet require PowerShell 5.0 or higher.
PowerShellGet is the module that provides the ability to install, update, and locate modules and scripts in repositories like the PowerShell Gallery. The previous version of this module includes cmdlets like Install-Module, Find-Module and Save-Module.
PowerShell 6.0 shipped with version 1.6.0 of PowerShellGet. PowerShell 7.0 shipped with version 2.2.3 of PowerShellGet. The current supported version of PowerShellGet is 2.2.5.
If you are running PowerShell 6 or higher, you have a usable version of PowerShellGet. If you are running Windows PowerShell 5.1, you must install a newer version.
Official Documents – https://github.com/PowerShell/PowerShellGet
What’s new in PowerShellGet v3?
PowerShellGet v3 is a completely rewritten implementation of the module. It provides more generic PSResource cmdlets rather than Install-Module or Save-Script. The new version is intended to improve the maintainability of the codebase which in turn should help address issues with the previous version of the module.
Managing Resources with PowerShellGet v3
The cmdlet names have changed in PowerShellGet v3. Instead of Install-Module, you will use Install-PSResource. It’s actually the same cmdlet for all resources such as scripts and DSC resources.
$ Install-PSResource -Name Universal
The Install-PSResource cmdlet supports similar parameters to Install-Module but have slightly different names and meanings.
For example, -AllowClobber was optional in Install-Module but is now the default for Install-PSResource. You can use -NoClobber to change this behavior.
$ Install-PSResource -Name dbatools -Version ‘1.1.41’ -NoClobber
How to install PowerShellGet?
Copy and Paste the following command to install PowerShellGet using Powershell with admin mode.
$ Install-Module -Name PowerShellGet -Force
$ Get-Command Install-Module
Update the PowerShellGet module to the latest version by running the following command:
$ Update-Module PowerShellGet -Force
$ Get-Command Install-Module
Close Powershell command line and open again with following commands...
$ Get-Command Install-Module
To install this preview release side-by-side with your existing PowerShellGet version, open any PowerShell console and run:
$ Install-Module PowerShellGet -Force -AllowPrerelease
To register the PSGallery run the command:
$ Register-PSResourceRepository -PSGallery
If you run the command Get-Command -Module PowerShellGet you will get a good picture of the side-by-side cmdlet interfaces.
After installing PowerShellGet
After you have installed the new version of PowerShellGet, you should open a new PowerShell session. PowerShell automatically loads the newest version of the module when you use a PowerShellGet cmdlet.
We also recommend that you register the PowerShell Gallery as a trusted repository. Use the following command:
$ Set-PSRepository -Name PSGallery -InstallationPolicy Trusted
PowerShellGet is the module that provides the ability to install, update, and locate modules and scripts in repositories like the PowerShell Gallery. The previous version of this module includes cmdlets like Install-Module, Find-Module and Save-Module.
Table of Implemented Parameters in this Release
| Cmdlet | Implemented parameters | Not implemented |
| Install-PSResource | -Name-Version-Prerelease-Repository-Credential-Scope-Reinstall | -InputObject-DestinationPath [partially implemented]-NoClobber-IgnoreDifferentPublisher-TrustRepository-Force [there hasn’t been a need for force yet since the things you would force aren’t implemented]-Quiet-AcceptLicense-PassThru |
| Update-PSResource | -Name-Version-Prerelease-Credential-Repository [Update should be discovering the repository from the xml metadata instead of from user input, this will be fixed in future releases] | -InputObject-UpdateTo-Force-Quiet-AcceptLicense-PassThru |
| Find-PSResource | -Name-Type-Version– Prerelease-ModuleName-Tags-Repository-Credential-IncludeDependencies | [Nothing] |
| Uninstall-PSResource | -Name-Version-PrereleaseOnly | [Nothing] |
| Save-PSResource | -Name-Version-Prerelease-Repository-Credential-AsNupkg-Path | -AcceptLicense |
| Get-PSResource | -Name-Version | -Prerelease |
| Register-PSResourceRepository | -Name-URL-PSGallery-Credential [credential persistence has not been implemented yet so this parameter is not currently being passed to anything]-Trusted-Priority | -Repositories-Proxy[for any proxies other than the default proxy]-ProxyCredential[see above regarding -Proxy] |
| Unregister-PSResourceRepository | -Name | [Nothing] |
| Get-PSResourceRepository | -Name-URL-Credential-Trusted-Priority | -Repositories-Proxy [for any proxies other than the default proxy]-ProxyCredential [see above regarding -Proxy] |
- DevOps Certified Professionals (DCP)
- Site Reliability Engineering Certified Professionals (SRECP)
- Master in DevOps Engineering (MDE)
- DevSecOps Certified Professionals (DSOCP)
URL - https://www.devopsschool.com/certification/
My Linkedin - https://www.linkedin.com/in/rajeshkumarin
- Apache Lucene Query Example - April 8, 2024
- Google Cloud: Step by Step Tutorials for setting up Multi-cluster Ingress (MCI) - April 7, 2024
- What is Multi-cluster Ingress (MCI) - April 7, 2024
