Make cachier optional #101
Conversation
pip seems to be required for development style installs Ansible chokes on the yaml stdout_callback
greg-hellings
force-pushed
the
make_cachier_optional
branch
from
9838e0f
to
5813df6
Compare
|
I've rebased this on top of #102 so that we can see test results here. |
There was a problem hiding this comment.
As said in #100 (comment), I'm worried about the maintainance of vagrant-cachier. So, maybe disable cachier by default would be a thing but this may possibly silently break things for users :(
At least, with this PR, things remains the same, while allowing to disable cachier.
|
Cachier still works for me. It's not getting knowledge of new package types, obviously, but I haven't had any issues with it. |
|
I can't see the logs from the ansible/check failures, but I'm happy to address them if I can. |
|
The check failure is on zuul and it was a timeout and I bet it was some kind of "glitch" so nothing to do except running the checks again to see if it happens again |
ok. nice. So, if it's still working, I'm happy with the current PR, as long as the checks are happy too |
|
recheck |
1 similar comment
|
recheck |
|
This time the Ubuntu test passed, but the linter timed out. Resource contention issues? 😆 |
|
I would call it zuul-gambling... let me remove the linters at least, two failures in a single day is far more than I am willing to deal with. |
Fixes #100