Downloads:

44

Downloads of v 2.6.2:

44

Last Update:

11 Dec 2019

Package Maintainer(s):

Software Author(s):

  • Ildar Shaimordanov

Tags:

psubst batchfile disk-management persistent-drive

psubst

2.6.2 | Updated: 11 Dec 2019

Downloads:

44

Downloads of v 2.6.2:

44

Maintainer(s):

Software Author(s):

  • Ildar Shaimordanov

psubst 2.6.2

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

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

>

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

>

To uninstall psubst, 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 psubst -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 psubst -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 psubst installed
  win_chocolatey:
    name: psubst
    state: present
    version: 2.6.2
    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 'psubst' do
  action    :install
  version  '2.6.2'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: psubst,
    Version: 2.6.2,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller psubst
{
   Name     = 'psubst'
   Ensure   = 'Present'
   Version  = '2.6.2'
   Source   = 'STEP 3 URL'
}

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


package { 'psubst':
  provider => 'chocolatey',
  ensure   => '2.6.2',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install psubst version="2.6.2" 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 gep13 on 07 Jan 2020.

Description

Associates a path with a drive letter and extends the standard SUBST command allowing to create persistent substituted drives between startups.


tools\chocolateyinstall.ps1
$dir = "$(Split-Path -Parent $MyInvocation.MyCommand.Definition)"
Install-BinFile -Name "psubst" -Path "$dir/psubst.bat"
tools\chocolateyuninstall.ps1
Uninstall-BinFile -Name "psubst"
tools\psubst.bat
@echo off


if "%~1" == "/?" (
	echo:%~n0 v2.6.2-2-g36ce939
	echo:
	echo:Associates a path with a drive letter.
	echo:Manages persistent substituted ^(virtual^) drives.
	echo:
	echo:PSUBST [drive1: [drive2:]path] [/P]
	echo:PSUBST drive1: /D [/P]
	echo:
	echo:  drive1:        Specifies a virtual drive to which you want to assign a path.
	echo:  [drive2:]path  Specifies a physical drive and path you want to assign to
	echo:                 a virtual drive.
	echo:  /D             Deletes a substituted ^(virtual^) drive.
	echo:  /P             Manages a persistent drives ^(create, delete, display^)
	echo:
	echo:Type PSUBST with no parameters to display a list of current virtual drives.
	goto :EOF
)


if "%~1" == "" (
	rem
	rem SUBST
	rem

	subst

	goto :EOF
)


if /i "%~1" == "/p" (
	rem
	rem SUBST /P
	rem

	setlocal enabledelayedexpansion
	setlocal enableextensions

	call :init

	call :print_persist

	call :cleanup

	endlocal
	goto :EOF
)


setlocal enabledelayedexpansion
setlocal enableextensions

call :init

call :init_disk "%~1"
call :init_path "%~2"

subst !psubst_disk! !psubst_path!

if /i "%~3" == "/p" (
	if /i "%~2" == "/d" (
		call :reg delete !psubst_disk! >nul
	) else (
		if errorlevel 1 goto stop_reg
		call :reg add !psubst_disk! !psubst_path! >nul
	)
)

:stop_reg
call :cleanup

endlocal
goto :EOF


:init
set psubst_disk=
set psubst_path=
set psubst_line=
set psubst_query="HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\DOS Devices"
goto :EOF


:init_disk
if "%~1" == "" goto :EOF
set psubst_disk=%~d1
if "!psubst_disk:~-1!" == "\" set psubst_disk=!psubst_disk:~0,-1!
goto :EOF


:init_path
if "%~1" == "" goto :EOF
if /i "%~1" == "/d" (
	set "psubst_path=%~1"
	goto :EOF
)

if /i "%~1" == "/p" (
	set psubst_path=
	for /f "tokens=1,2,*" %%a in ( 'reg query !psubst_query! ^| findstr ??' ) do (
		if "!psubst_disk!" == "%%~a" (
			set psubst_path="%%~c"
			set psubst_path=!psubst_path:\??\=!
			goto :EOF
		)
	)
	goto :EOF
)

set "psubst_path=%~1"
set psubst_path=!psubst_path:/=\!
if "!psubst_path:~-1!" == ":" set psubst_path=!psubst_path!\
if "!psubst_path:~-1!" == "\" (
	if not "!psubst_path:~-2,1!" == ":" set psubst_path=!psubst_path:~0,-1!
)

set psubst_path="!psubst_path!"
goto :EOF


:reg
set psubst_line=
if not "%~3" == "" (
	set "psubst_line=\??\%~3"
	if not "!psubst_line:~-1!" == "\" set psubst_line="!psubst_line!"
	set psubst_line=/t REG_SZ /d !psubst_line!
)
if not "%~2" == "" set psubst_line=/v %~2 !psubst_line!
if /i not "%~1" == "query" set psubst_line=!psubst_line! /f

reg %~1 !psubst_query! !psubst_line!
goto :EOF


:print_persist
for /f "tokens=1,2,*" %%a in ( 'reg query !psubst_query! ^| findstr ??' ) do (
	set psubst_disk=%%~a
	set psubst_path=%%~c
	set psubst_path=!psubst_path:\??\=!

	echo:!psubst_disk!\: =^> !psubst_path!
)
goto :EOF


:cleanup
set psubst_query=
set psubst_disk=
set psubst_path=
set psubst_file=
set psubst_line=

goto :EOF


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

This package has no dependencies.

Discussion for the psubst Package

Ground Rules:

  • This discussion is only about psubst and the psubst 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 psubst, 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