vagrant

Author	SHA1	Message	Date
Chris Roberts	c999e7c3d4	Update behavior of `snapshot restore` and `snapshot pop` Both of these commands failed to default the options disabling the provisioning from ignoring the sentinel file. This resulted in different behavior than what was seen with the `up` and `resume` commands which would only provision items with run set to "always". This defaults the options to proper match the behavior of `up` and `resume` to be consistent. This also adds an extra `--no-start` flag to allow users to restore a snapshot but not start the restored guest immediately. Fixes #6752	2018-12-07 16:17:44 -08:00
Jon Topper	eff2b2d7b4	Support provisioning flags on snapshot rollback	2016-01-16 16:07:57 +00:00
Jon Topper	7ba398ead8	Add --no-delete to 'snapshot pop' command In our test environments, it's good to be able to roll back to the same, anonymous, snapshot repeatedly. This patch adds a `--no-delete` option to the `snapshot pop` command allowing this. This makes the new core snapshot behaviour more consistent with what we were doing with vagrant-multiprovider-snap (https://github.com/scalefactory/vagrant-multiprovider-snap)	2016-01-15 18:21:47 +00:00
Mitchell Hashimoto	ed4df21c85	commands/snapshot: push and pop	2015-10-07 22:52:27 -04:00