-
Notifications
You must be signed in to change notification settings - Fork 189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow the ability to explicitly enable caching #346
Comments
Otherwise, just reference https://github.com/test-kitchen/kitchen-vagrant#-cache_directory and set |
If I'm reading this right, even if I specify https://github.com/test-kitchen/kitchen-vagrant/blob/master/lib/kitchen/driver/vagrant.rb#L252 |
That is correct, the feature is only supported on specific boxes we know it works on. |
Sure, but for cases where I know the feature works for a non-bento box, shouldn't there be a config option that I can explicitly allow it? Definitely understand if it's disabled by default. |
Mostly we didn't want to deal with the support burden because the caching system was more than a bit unstable at first. I think it had settled down enough that we would be open to a patch to allow it, though I'm not sure of the best approach. |
Happy to look at a patch, to be honest I thought we'd left it so that a user could explicitly set the dir still so I'm happy to fix this one. I was mostly cleaning up other folks code which was a bit more liberal about enabling as @coderanger mentions so this was probably erring on the side of safety at the time without realizing it. |
Do you have a preference for how it's implemented?
|
In my mind we should honor |
Signed-off-by: Seth Thomas <[email protected]>
With #303 cache is only available when using utilizing known bento boxes through a whitelist even though I'm explicitly specifying
cachier: true
. This took a while of digging as it was previously working on some Windows boxes.What is the correct course of action to allow the ability to utilize the cache when not using bento boxes? I'd be happy to slap in another config option if that's what's needed.
The text was updated successfully, but these errors were encountered: