I run this:

  - shell exec ./provisioner/
    -- ./provisioner/ exec ../modules/
    my trap the error code from ../modules/ so I am 
able to decide what to do after.

Le mardi 20 février 2018 09:40:28 UTC-5, Niko a écrit :
> I want my provisioner to catch certain return codes from my provisioning 
> script, but unfortunately Vagrant processes any non-zero codes as an 
> "error" (which is not the case). Is there any way to handle the exception 
> and continue instead?

This mailing list is governed under the HashiCorp Community Guidelines - Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues:
IRC: #vagrant on Freenode
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
To view this discussion on the web visit
For more options, visit

Reply via email to