forked from test-kitchen/test-kitchen
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add PowerShell/Windows support to ChefZero Provisioner.
HTTP Proxy ========== This commit also added more complete strategy for HTTP proxy variable setting. If both `:http_proxy` and `:https_proxy` are set, then the following Bourne shell environment variables are exported: * `http_proxy` * `HTTP_PROXY` * `https_proxy` * `HTTPS_PROXY` And the following PowerShell environment variables are set: * `$env:http_proxy` * `$env:HTTP_PROXY` * `$env:https_proxy` * `$env:HTTPS_PROXY` These environment variables will be set for every command excuted in the Chef-related Provisioners. The Bourne shell environment variable setting has also changed. Previously they were set with an `env` prepended to the `sh -c '...'` wrapped command. As of this commit, these environment variables are set inside the `sh -c '...'` at the top and are exported. For example running `wget "http://chef.io/chef/install.sh"` with `:http_proxy` and `:https_proxy` set would generate a command similar to: sh -c ' http_proxy="http://proxy"; export http_proxy HTTP_PROXY="http://proxy"; export HTTP_PROXY https_proxy="https://proxy"; export https_proxy HTTPS_PROXY="https://proxy"; export HTTPS_PROXY wget "http://chef.io/chef/install.sh" ' Legacy Chef Zero Shim ===================== As has always been the case, the chef-zero shim strategy for versions of Chef older than 11.8.0 is best-effort, meaning it will work if your base image has the needed requirements (which sometimes involve a compiler).
- Loading branch information
Showing
4 changed files
with
618 additions
and
310 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.