mirror of
https://github.com/hashicorp/vagrant.git
synced 2026-02-16 00:58:17 -05:00
eacb798a71
The "destroy_on_error" functionality for `vagrant up` is implemented in the `recover()` action chain, and works by firing off a destroy action from inside that chain. This is all well and good, but it copies its existing `env` which has had `action_name` set for the up action. This was causing action_hooks for up actions to attach to this destroy action stack. Setting the action_name explicitly in the env before firing the runner should correct the behavior. I'm not sure if raw_action_name is used anywhere but I figured it was better to be consistent vs conservative in what we change. |
||
|---|---|---|
| .. | ||
| docker | ||
| hyperv | ||
| virtualbox | ||