Skip to content
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

Support box_version option #102

Merged
merged 2 commits into from
Nov 10, 2014
Merged

Conversation

mconigliaro
Copy link
Contributor

Vagrant has supported box versioning since v1.5. Although it doesn't seem to be well documented, it's actually possible to set box_url to a metadata file rather than a specific box. This PR makes kitchen-vagant support Vagrant's box_version option, without which, Vagrant will default to using the latest version.

This will be very useful to teams who have a large number of proprietary Chef cookbook repositories. Now instead of having to update the .kitchen.yml in every repo for every new base box update, it'll be possible to do global updates through a single metadata file hosted on a server.

@sethvargo
Copy link
Contributor

👍

sethvargo added a commit that referenced this pull request Nov 10, 2014
@sethvargo sethvargo merged commit 39fb1ff into test-kitchen:master Nov 10, 2014
@sethvargo
Copy link
Contributor

W00t w00t

@mconigliaro
Copy link
Contributor Author

Thanks for the merge. In the time since I created this, I realized that Vagrant won't actually update the box until you run vagrant box update. You can do this manually of course (e.g. cd .kitchen/kitchen-vagrant/<vm> && vagrant box update), but this is a good example where test-kitchen/test-kitchen#350 would help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants