You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 11, 2022. It is now read-only.
I'm trying to use vagrant-aws plugin w/ vagrant-triggers plugin and seeing unexpected behavior.
If you do this
vagrant up --provider aws
with the Vagrantfile below then the trigger does not fire.
Do
vagrant up
and trigger fires as expected.
I'm guessing the 'up' is intercepted by the vagrant-aws plugin when aws is the default provider and it's more likely a vagrant-triggers plugin issue.
Any easy way around this?
Vagrant.configure("2") do |config|
config.vm.box = "docker-server"
config.trigger.before :up do
confirm = nil
until ["Y", "y", "N", "n"].include?(confirm)
confirm = ask "Would you really like to bring up the VM? (Y/N) "
end
exit unless confirm.upcase == "Y"
end
config.vm.provider :aws do |aws, override|
end
end
The text was updated successfully, but these errors were encountered:
I'm trying to use vagrant-aws plugin w/ vagrant-triggers plugin and seeing unexpected behavior.
If you do this
with the Vagrantfile below then the trigger does not fire.
Do
and trigger fires as expected.
I'm guessing the 'up' is intercepted by the vagrant-aws plugin when aws is the default provider and it's more likely a vagrant-triggers plugin issue.
Any easy way around this?
The text was updated successfully, but these errors were encountered: