graceful renaming of vagrant nodes
two problems with renaming a vagrant node with leap node mv
:
the local vagrant virtual machine will still be running under the old name. simple solution is to automatically run leap local destroy.
when you commit your changes, the other people will not have an easy way to destroy the old vagrant virtual machines, unless they know to run 'local destroy' before they pull. not sure what the solution is to this.
(from redmine: created on 2012-12-18)