Downloads:

29,382

Downloads of v 1.0.4.407:

21,830

Last Update:

29 Dec 2015

Package Maintainer(s):

Software Author(s):

  • Mike Chaliy

Tags:

PsGet install modules powershell

PsGet Utils

1.0.4.407 | Updated: 29 Dec 2015

Downloads:

29,382

Downloads of v 1.0.4.407:

21,830

Maintainer(s):

Software Author(s):

  • Mike Chaliy

Tags:

PsGet install modules powershell

PsGet Utils 1.0.4.407

Some Checks Have Failed or Are Not Yet Complete

1 Test Passing and 1 Failing Test

Hide Checks
Hide Checks

Validation Testing Passed

Verification Testing Failed

Details

To install PsGet Utils, run the following command from the command line or from PowerShell:

>

To upgrade PsGet Utils, run the following command from the command line or from PowerShell:

>

To uninstall PsGet Utils, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade psget -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade psget -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode


- name: Ensure psget installed
  win_chocolatey:
    name: psget
    state: present
    version: 1.0.4.407
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'psget' do
  action    :install
  version  '1.0.4.407'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: psget,
    Version: 1.0.4.407,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller psget
{
   Name     = 'psget'
   Ensure   = 'Present'
   Version  = '1.0.4.407'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'psget':
  provider => 'chocolatey',
  ensure   => '1.0.4.407',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install psget version="1.0.4.407" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator ferventcoder on 29 Dec 2015.

Description

Set of commands to install PowerShell modules from central directory, local file or from the web.

Features:
1.Install modules from central directory
2.Install modules from web or local file
3.Install modules to user profile or for all users ( elevated access required )
4.Install multifile modules from ZIP
5.Import module after install
6.Alter you profle to load module every time that PowerShell starts
7.Execute Install.ps1 if found in module folder
8.Tab completion for modules, ismo Ps

tools\chocolateyInstall.ps1 
function Add-PathToEnvironmentVariable {
    param(
	[Parameter(Mandatory=$true)]
	[string]$variableName, 
	[ValidateSet("Machine", "User")]
	[string]$Scope = "User",
	[Parameter(Mandatory=$true)]
	[string]$pathToAdd)

    $existingValue = [Environment]::GetEnvironmentVariable($variableName, $Scope)
    Write-Verbose "The existing value of the '$Scope' environment variable '$variableName' is '$existingValue'"
    $pathToAdd = [io.path]::GetFullPath(($pathToAdd.Trim() + '\'))
	Write-Verbose "Path: $pathToAdd"
	$paths = $existingValue.ToLower().Split(";")
	$doesPathAlreadyExist = $false
	foreach($path in $paths) {
	   $path = [io.path]::GetFullPath(($path.Trim() + '\'))

		Write-Verbose @"
Compare paths:
Existing path: $path
New path:      $pathToAdd

"@
		if($path -like $pathToAdd) {
			$doesPathAlreadyExist = $true;
			Write-Warning "The path '$pathToAdd' is already in the environment variable '$variableName'.  The path will not be added."
		} 
	}
  
    if(-not $doesPathAlreadyExist) {
    	$existingValue += ";$pathToAdd"
       
        [Environment]::SetEnvironmentVariable($variableName,$existingValue, $Scope)

        sc env:\$variableName ([Environment]::GetEnvironmentVariable($variableName, $Scope) + ";" + [Environment]::GetEnvironmentVariable($variableName, "User"))
        $newValue = gc env:\$variableName
        Write-Verbose "The new value of the '$Scope' environment variable '$variableName' is '$newValue'"
        
    }

}
$PsGetDestinationModulePath = "$env:ProgramFiles\WindowsPowerShell\Modules"
Add-PathToEnvironmentVariable -variableName "PSModulePath" -scope "Machine" -pathToAdd $PsGetDestinationModulePath

(new-object Net.WebClient).DownloadString("http://psget.net/GetPsGet.ps1") | iex

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
PsGet Utils 1.0.4.407 21830 Tuesday, December 29, 2015 Approved
PsGet Utils 1.0.4.310 3541 Friday, July 25, 2014 Unknown
PsGet Utils 1.0.4.297 453 Friday, June 27, 2014 Unknown
PsGet Utils 1.0.4.292 524 Wednesday, May 21, 2014 Unknown
PsGet Utils 1.0.4.283 429 Thursday, May 1, 2014 Unknown
PsGet Utils 1.0.4.281 478 Monday, April 7, 2014 Unknown
PsGet Utils 1.0.4.279 470 Monday, March 10, 2014 Unknown
PsGet Utils 1.0.4.277 337 Thursday, February 20, 2014 Unknown
PsGet 1.0.3 823 Thursday, May 30, 2013 Unknown
PsGet 1.0.0 497 Wednesday, May 29, 2013 Unknown

Updated install location to match Microsoft pathing of C:\Program Files\WindowsPowerShell\Modules\

This package has no dependencies.

Discussion for the PsGet Utils Package

Ground Rules:

  • This discussion is only about PsGet Utils and the PsGet Utils package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or PsGet Utils, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus