Update to Vagrant 2.1.x, use built-in vagrant snapshot command #28
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gep13
reviewed
Jul 27, 2018
|
Thanks @gep13 for checking the vagrant command. Yes, I used |
|
Awesome work @StefanScherer! Thanks for your contribution! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I used the choco test environment with Vagrant 2.1.2 and VirtualBox 5.2.x on my Mac. So I skipped the sahara plugin and just used the built-in
vagrant snapshotcommand.Here are the steps I did instead.
The
vagrant snapshot restorestill runs the provision script by default (which my be useful here). This will change in the future that no provision script is called automatically.