Warning message on vagrant halt

[HeathNaylor]

It seems far too easy to accidentally run harmful vagrant operations on production environments provisioned with Vagrant. Any way to add warnings or disable behaviors?

[displague]

If you do happen to 'vagrant destroy -f' Linode support can undo the damage if you contact them soon after. Reconnecting that Linode to your vagrant file would involve recreating the files in .vagrant/machines (might be worth backing this directory up if you are using vagrant-linode for production machines rather than development).

• .vagrant/machines/default/linode/id
• .vagrant/machines/default/linode/creator_uid
• .vagrant/machines/default/linode/index_uuid

That said, vagrant destroy prompts. Is vagrant halt (a shutdown) really harmful / destructive?

[HeathNaylor]

If you compromise server up-time (SLA) then yes, it is harmful.

[displague]

This could be doable with a config option that would force halt to prompt or fail. (disable_halt = true)

I'd really like to see more interest in this idea before proceeding with it. This still seems like a more general vagrant (upstream) concern, than something vagrant-linode should be concerned with.