» Vagrant Triggers

Each trigger is expected to be given a command key for when it should be firedduring the Vagrant command lifecycle. These could be defined as a single key oran array which acts like a whitelist for the defined trigger.

Alternatively, the key could be given which would run the trigger beforeor after every Vagrant command. If there is a command you don't want the triggerto run on, you can ignore that command with the ignore option.

Triggers can be defined as a block or hash in a Vagrantfile. The example belowwill result in the same trigger:

Triggers can also be defined within the scope of guests in a Vagrantfile. Thesetriggers will only run on the configured guest. An example of a guest only trigger:

In this generic case, the triggers would fire in the order: 1 -> 2 -> 3 -> 4

For more information about what options are available for triggers, see the.