This repository has been archived by the owner on Jan 6, 2023. It is now read-only.
Add option to disable vagrant-cachier #100
Comments
greg-hellings
added a commit
to greg-hellings/molecule-vagrant
that referenced
this issue
Apr 19, 2021
Merged
greg-hellings
added a commit
to greg-hellings/molecule-vagrant
that referenced
this issue
Apr 20, 2021
|
When working on the vagrant.yml removal thing, I've not dealt with cachier because it was an unrelated change but I had this plugin in my mind for quite some time. At minimum, making it optional is a good idea, but I've been wondering about doing more than that. Cachier has not been maintained for quite some time (fgrehm/vagrant-cachier#143) so I'm even wondering if it's still working correctly |
ssbarnea
added a commit
that referenced
this issue
Apr 21, 2021
* Make tests run pip seems to be required for development style installs Ansible chokes on the yaml stdout_callback * Make cachier optional Fixes #100 * Document the option Co-authored-by: Sorin Sbarnea <ssbarnea@redhat.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently the generated Vagrantfile checks for the presence of the cachier plugin, and configures it if it is found.
However, it's very possible that this plugin could be installed on some hosts, but not others, and a user might want to explicitly disable this. Provide an option to allow that.
The text was updated successfully, but these errors were encountered: