Another example to add please

[kalefranz]

Hi @emyl . Thanks for the awesome plugin. It's really very helpful.

I'm not a Ruby guy, so like a lot of other people here, examples are good. In my specific situation, writing a config.trigger.before :provision block only triggers when I run vagrant provision. I'd really like that block to hit when I run any of

• vagrant provision
• vagrant up --provision
• the first vagrant up when the provision step us run
• if any config.vm.provision block is set to run: "always"

Is there something straight-forward I can do to make this happen?

[emyl]

Hi!

That's an interesting use case! Let me think a moment how it can be implemented... :wink:

[ypereirareis]

Hi,

I'm interesting in this possibility or implementation too... Are you still looking at it ?

Thanks

[svenXY]

Hi,

I have the exact same requirement.

Specifically, I want to run jpetazzo/pipework to create additional network interfaces.

After vagrant halt && vagrant up, they are gone, thus it would be great if I could recreate them as soon as possible (i.e. before the puppet provisioner runs).

It seems currently not possible to trigger something to run

• after :up, but
• before :provision
• in the initial vagrant up run, which implies provisioning

Thanks, Sven

[pcriv]

+1

[emyl]

Starting from version 0.5.0, just released, triggers could be run as a provisioner too:

config.vm.provision "trigger", :option => "value" do |trigger|
  trigger.fire do
    run "script"
  end
end

[pcriv]

how is this different from 'shell' provisioner?

[emyl]

@pablocrivella shell provisioner runs only on the guest, this one could run both on the host and the guest.

[pcriv]

aaah hehe right! :sweat_smile: thanks @emyl