vagrant/plugins/commands/snapshot/command
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
..
delete.rb (#7188) Clean up vagrant snapshot restore/delete error messages 2017-06-07 09:12:20 -07:00
list.rb Raise exception if provider doesn't have snapshot capability 2017-05-26 15:22:25 -07:00
pop.rb Update behavior of `snapshot restore` and `snapshot pop` 2018-12-07 16:17:44 -08:00
push.rb commands/snapshot: push and pop 2015-10-07 22:52:27 -04:00
push_shared.rb Fix up style nit. 2016-03-04 17:35:54 +00:00
restore.rb Update behavior of `snapshot restore` and `snapshot pop` 2018-12-07 16:17:44 -08:00
root.rb snapshot plugin: Raise error for bad subcommand. 2018-12-01 14:44:42 -05:00
save.rb Raise exception if provider doesn't have snapshot capability 2017-05-26 15:22:25 -07:00