Hello,

when I run the "Boot up Vagrant VM" step, it also provision the vagrant with what is defined in the Vagrantfile.
The step "Provision a Vagrant VM" allows to define a provisioner but not the associated options (e.g. for Salt "minion_id" https://www.vagrantup.com/docs/provisioning/salt.html).
So it means that needed options must be in the Vagrantfile.

I found the actual behaviour confusing or not clear enough: if I define provisioning in Vagrantfile it gets launched at boot, so I can't have an additional step between boot and provision.
If the provisioning is not defined in Vagrantfile, it can't be done because the form only have one field for the name not the options.

I can imagine a boot step with no provisioning (with --no-provision option) so that provisioning is only done if a specific provision step is defined.

Thanks for your answer. I hope it don't misunderstand the way this plugin can/must be used.