Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
-
Modules
-
3
-
Modules Triage, Modules 2016-12-14, Modules 2017-01-11, Modules 2017-01-25, Modules 2017-02-08
-
Automate
Description
In newer versions of PowerShell, it looks like environment variables are not getting passed through.
exec { 'test environment variables':
|
command => 'Write-Output "TESTVALUE = $env:TESTVALUE"',
|
provider => powershell,
|
logoutput => true,
|
environment => ["TESTVALUE=YES"],
|
}
|
Tested against 2.0.0 up to 2.1.0 and this was returned every time.
Notice: /Stage[main]/Exec[test envvars]/returns: TESTVALUE =
|
In version 1.0.6, the return looks like this:
Notice: /Stage[main]/Exec[test envvars]/returns: TESTVALUE = YES
|
Attachments
Issue Links
- blocks
-
MODULES-5163 Supported Release (powershell) 2.1.1 - (7 Jul 2017) - (7d818f7cd75224f60ba10dbf048b6be0e8d0dd26)
-
- Resolved
-
- relates to
-
MODULES-3709 PowerShell module 2.x - Does not Respect Timeout
-
- Resolved
-
-
MODULES-4149 When Chocolatey is not installed, configuration resources kill puppet run
-
- Resolved
-
-
MODULES-3280 Powershell - Remove Verbose Environment Variable Setting
-
- Resolved
-
-
MODULES-4091 When using alternate chocolatey install directory, ChocolateyInstall does not get set.
-
- Resolved
-