Disable vagrant-cachier caching by default, but allow to opt-in #85
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.
While preparing the exercises I saw quite a few vagrant-cachier related errors surfacing, especially when working with multi-vm Vagrantfiles.
Since this is highly confusing for new users, I disabled the caching that was enabled by default in
~/.vagrant.d/Vagrantfile
.You now have to explicitly opt-in to having vagrant-cachier caches enabled by default by the
$GLOBAL_VAGRANT_CACHIER_ENABLED
env var to any value, e.g.:To opt-out again, you have to unset the env var: