End-users cannot intuitively discover what triggers are available to use?

emyl / vagrant-triggers

Allow the definition of arbitrary scripts that will run on the host before and/or after Vagrant commands.

MIT License

546 stars 35 forks source link

Closed mlintonford closed 6 years ago

mlintonford commented 8 years ago

Apart from the up, destroy, halt, and resume shown in Readme.md, end-users cant intuitively discover triggers.

Could be solved by link to some type of triggers list in vagrant github

javadevmtl commented 8 years ago

Yes. I'm trying different actions and they don't seem to fire.

Does it also mean the third party provisioner like the vSphere vagrant also have to implement the action?

brianfgonzalez commented 7 years ago