Closed Sharpie closed 8 years ago
@Sharpie I suppose you use the Chef client provisionner ? Up to now it seems to be the only one that implement this feature. Unfortunately i don't have an up and running Chef server to test it on my side. Can you confirm you successfully tested it with the Chef client provisionner ?
I use a Puppet provisioner which de-registers a machine that is being destroyed, along with a hostname provisioner that manages /etc/hosts
and removes a machine's entries from other nodes when it is destroyed.
I also use multiple providers on a regular basis: VirtualBox, AWS, OpenStack, vSphere. So, having consistent provisioner cleanup behavior between all is important as well.
Vagrant v1.3.0 introduced the ability for provisioners to define cleanup tasks that get run during VM destruction in order to clean up bits of global state. This patch adds the ProvisionerCleanup task to the OpenStack destroy action.