Add installer_download_path
config option to chef provisioners
#5002
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds the
installer_download_path
config option to all chef provisioners. It is effective only when the Chef auto-install feature is used.Example Vagrantfile:
This will ensure that the omnibus package is downloaded to the given directory (i.e.
/tmp/vagrant-cache/vagrant_omnibus/chef_12.0.1-1_amd64.deb
in this case).It is a prerequisite for enabling caching of the omnibus packages via vagrant-cachier (see #4989).
For further details and context:
-d
and-f
flag to install.sh: Cache omnibus download chef/omnitruck#33-d
and-f
flag in the official docs: Some command line options for omnitruck install.sh are missing in the documentation chef-boneyard/chef-web-docs-2016#429Within this PR I only added support for the
-d
flag as this is the only thing required for enabling caching. So far I never needed the-f
option. Sacrificing completeness for YAGNI here ;-)