57 Commits (7efe3cac3d5e728ee471bbccfd1043e06e4dcafe)

Author	SHA1	Message	Date
Megan Marsh	b35acbd879	use statebag instead of SetSharedState for winRM password	8 years ago
Megan Marsh	ff6a039d5b	replace scrubconfig with packer.LogSecretFilter.Set ... filter winrm password from logs Add new root-level packer template option, sensitive-variables, to tell us what user variables to mark sensitive.	8 years ago
DanHam	485d565e32	Ensure comments are easily readable in a standard terminal	8 years ago
DanHam	e0bcba4913	Make the upload of env vars retryable in case of restarts	8 years ago
DanHam	b9ab2c8048	Remove script containing PowerShell inline commands from local tmp when done	8 years ago
DanHam	5419375413	Change to CMD % style path is no longer required	8 years ago
DanHam	5b652316d9	Dollar's in env vars used in paths may cause problems for ssh ... * Dollars are interpreted by *nix shells so paths using env vars such as ${env:SYSTEMROOT} will cause issues	8 years ago
DanHam	4e7feea184	Allow users to specify the location that the env vars file is uploaded to ... Previously the location the file was uploaded to was set internally and used ${env:SYSTEMROOT}/Temp as the destination folder. By default, in order to inject the required environment variables, the file is 'dot sourced' by the 'execute_command' using the {{ .Vars }} variable. Unfortunately the inclusion of the dollar in the path caused issues for users connecting over ssh as the (typically bash) shell running the execute command would try and interpret the dollar sign. The change allows users to specify the location the file is uploaded to, thereby allowing the user to specify a custom 'execute_command' that escapes any dollar signs that could be present in the path. If not set the upload path now defaults to using C:/Windows/Temp as the upload folder.	8 years ago
Megan Marsh	3afb243f11	use build name to ensure that winrm password and other shared state is not overwritten if two builders need the password in the same packer run.	8 years ago
DanHam	ef4817d644	Fix vertical spacing	8 years ago
DanHam	34db6c4ab1	Remove temp debugging output	8 years ago
Megan Marsh	4e321b2dfa	don't need to use a receiver with this function	8 years ago
Megan Marsh	ce1ab1f021	fix winrm password	8 years ago
Megan Marsh	559719020c	use {{.WinRMPassword}} instead of some other weirdness	8 years ago
Megan Marsh	d689e6b4d3	allow users of AWS to use the dynamically-generated admin password which we use as the winRM password as an elevated password in the Powershell provisioner, as well as an environment variable in same provisoner.	8 years ago
Josh Soref	04d6bfc696	spelling: environment	8 years ago
Megan Marsh	3faf73b5f3	change backslashes to forward slashes in powershell provisioner; was breaking with cygwin	8 years ago
DanHam	2d830d5d43	Auto escape chars special to PowerShell in user supplied data	8 years ago
DanHam	478589abec	Extend upload and subsequent 'dot sourcing' of env vars to std PS command ... * Wrap funcs to flatten and upload env vars with new func prepareEnvVars. While the wrapped funcs could be combined, keeping them separate simplifies testing. * Configure/refactor std and elevated PS to use new funcs to prepare, upload and dot source env vars. * Dot sourcing the env vars in this way avoids the need to embed them directly in the command string. This avoids the need to escape the env vars to ensure the command string is correctly parsed. * Characters within the env vars that are special to PS (such as $'s and backticks) will still need to be escaped to allow them to be correctly interpreted by PS. * The std and elevated PS commands now inject env vars into the remote env via the same mechanism. This ensures consistent behaviour across the two command types. Fixes #5471	8 years ago
Megan Marsh	addedbb680	Revert "Merge pull request #5515 from DanHam/dot-source-env-vars" ... revert so we can use a branch that's had more recent work done This reverts commit e56849c605, reversing changes made to 6d14eb6ea4.	8 years ago
Megan Marsh	79fe900378	Revert "Merge pull request #5376 from DanHam/ps-escapes" ... Revert so that we can merge a different branch that's had more recent work instead This reverts commit ba518637d4, reversing changes made to e56849c605.	8 years ago
DanHam	7443adf2fd	Simpler escape of chars special to PowerShell in user supplied data	8 years ago
DanHam	68e13c90b1	Revert "Escape chars special to PowerShell in user supplied data" ... This reverts commit 53aefe744bcd74ee6ac866f764eafe9e7f507d80.	8 years ago
DanHam	f3c326bb3c	Escape chars special to PowerShell in user supplied data	8 years ago
DanHam	5949bc91c4	Extend upload and subsequent 'dot sourcing' of env vars to std PS command ... * Wrap funcs to flatten and upload env vars with new func prepareEnvVars. While the wrapped funcs could be combined, keeping them separate simplifies testing. * Configure/refactor std and elevated PS to use new funcs to prepare, upload and dot source env vars. * Dot sourcing the env vars in this way avoids the need to embed them directly in the command string. This avoids the need to escape the env vars to ensure the command string is correctly parsed. * Characters within the env vars that are special to PS (such as $'s and backticks) will still need to be escaped to allow them to be correctly interpreted by PS. * The std and elevated PS commands now inject env vars into the remote env via the same mechanism. This ensures consistent behaviour across the two command types. Fixes #5471	8 years ago
DanHam	8214a12a2a	Move append of portion of command used to send elevated PS output to file	9 years ago
DanHam	2a060adbf8	Don't use -EncodedCommand with PS as progress stream always leaks to stderr ... * Setting $ProgressPreference to SilentlyContinue makes no difference when -EncodedCommand is used - any output to the progress stream still appears on stderr. * Delete file containing encode/decode functions since we no longer need them. * Fixes leak of output on progress streams for both normal and elevated commands. * Since we no longer base64 encode, ensure any characters special to XML are correctly escaped in the elevated command. This ensures correct parsing once the command is wrapped within the elevatedTemplates XML based Task Scheduler definition. Fixes #4322	9 years ago
DanHam	5374c6e367	Use system context env var to set path for elevated PS env vars file	9 years ago
Matthew Hooker	af1187d5e1	simplify a bit	9 years ago
Megan Marsh	cbe1d7d854	simplify file upload for elevated powershell wrapper	9 years ago
Megan Marsh	92e70757bb	Move env vars into a file that we dot-source instead of trying to write them all to the command line	9 years ago
Megan Marsh	d458628529	exclude elevated_executed_command from config interpolation so it can be used correctly later	9 years ago
Megan Marsh	c6889ad009	clarify logging by changing 'shell' to 'powershell' inside of the powershell provisioner	9 years ago
Megan Marsh	b2923b4da6	check stdout to make sure echo command actually goes through before counting computer as fully restarted	9 years ago
Megan Marsh	5214851463	make every script name unique	9 years ago
Matthew Hooker	81522dced0	move packer to hashicorp	9 years ago
Matthew Hooker	0149f679de	Print instead of Printf with no dynamic first variable.	9 years ago
DanHam	4122f3a897	provisioner/powershell: Remove env var check - we already check in Prepare	9 years ago
Matthew Hooker	480398c3d2	only set PACKER_HTTP_ADDR if a server is listening	9 years ago
Matthew Hooker	6563eb213c	Document. add to windows-shell and powershell	9 years ago
DanHam	0423f91037	Fix to allow equals sign in value of environment variable	9 years ago
Taliesin Sisson	e36051d394	Pattern for infrastructure changed to quote filename and execute file with ampersand as everything is run in powershell now ... Handle powershell commands by specifying any extra infrastructure around running scripts inside of ExecuteCommand and ElevatedExecuteCommand	9 years ago
Taliesin Sisson	d61513bf77	Encode powershell using utf8 ... Fix a bug in the size of string that was returned when decoding a base64 string Added tests around encoding and decoding powershell scripts. Used [System.Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes('powershell commands')) | clip to generate what base 64 strings should look like	9 years ago
Taliesin Sisson	17597b48e1	Base64 encode powershell to avoid any necessary escaping	9 years ago
Taliesin Sisson	5d5809b27e	Make hiding of progress backward compatible with old versions of powershell	9 years ago
Taliesin Sisson	e8c2b49be8	Use correct quotation of variables	9 years ago
Taliesin Sisson	4b394c8563	Write output will put ouput from function, so we don't want to be getting line from output of function ... Fix unit tests for not showing progress stream when using powershell Ensure that progress stream does not get leaked into stdout Using Write-Output instead of Write-Host since PS v5 now leaks the host stream to stderr	9 years ago
Taliesin Sisson	cd6213eb55	Seems like we do need to escape the double quote	9 years ago
Taliesin Sisson	5285a819dd	Quoting of powershell commands and associated tests	9 years ago
Taliesin Sisson	3051ea6633	Quote powershell so that it does not try to interpret command to be run ... Get VName out of state. This allows template replacement to be run on vmname	9 years ago