haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Add more information about Ruby trigger option 

This commit provides a bit more context to using the new Ruby trigger
option.
This commit is contained in:
Brian Cain 2018-10-08 09:47:03 -07:00
parent 9ee153802a
commit af91b3bb2f
No known key found for this signature in database
GPG Key ID: 9FC4639B2E4510A0
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/source/docs/triggers/configuration.html.md
View File

@ -34,7 +34,7 @@ The trigger class takes various options.
* `only_on` (string, regex, array) - Limit the trigger to these guests. Values can be a string or regex that matches a guest name.
* `ruby` (block) - A block of Ruby code to be executed. Can only be a `Proc` type. Two optional arguments may be passed into the given block: `env` and `machine`. These options correspond to the environment used, and the machine that the trigger is firing on. If no options are provided to the block, then they will not be available to be used with your Ruby code.
* `ruby` (block) - A block of Ruby code to be executed on the host. The block accepts two arguments that can be used with your Ruby code: `env` and `machine`. These options correspond to the Vagrant environment used (note: these are not your shell's environment variables), and the Vagrant guest machine that the trigger is firing on. This option can only be a `Proc` type, which must be explicitly called out when using the hash syntax for a trigger.
```ruby
ubuntu.trigger.after :up do |trigger|