diff --git a/website/source/docs/triggers/configuration.html.md b/website/source/docs/triggers/configuration.html.md index c700eedbf..786ac1106 100644 --- a/website/source/docs/triggers/configuration.html.md +++ b/website/source/docs/triggers/configuration.html.md @@ -27,7 +27,7 @@ config.trigger.before :up do |t| end ``` -Triggers can be used with [_actions_](#actions) or [_commands_](#commands) as well, +Triggers can be used with [_actions_](#actions), [_hooks_](#hooks), or [_commands_](#commands), but by default will be defined to run before or after a Vagrant guest. ## Trigger Options @@ -124,6 +124,8 @@ __Note:__ Triggers _without_ the type option will run before or after a Vagrant guest. These most similarly align with the `:action` type, and by default are classified internally as an action. +TODO: ADD INFO ABOUT GUARDING TYPE OPTION WITH VAGRANT VERSION CHECK IN VAGRANTFILE FOR OLDER CLIENTS + ### Commands Command typed triggers can be defined for any valid Vagrant subcommand. They will always @@ -139,6 +141,14 @@ The difference between this and the default behavior is that these triggers are not attached to any specific guest, and will always run before or after the given command. +### Hooks + +