Skip to content
This repository has been archived by the owner on Feb 11, 2022. It is now read-only.

triggers are ignored when provider is 'aws' #233

Closed
russroy opened this issue May 17, 2014 · 1 comment
Closed

triggers are ignored when provider is 'aws' #233

russroy opened this issue May 17, 2014 · 1 comment

Comments

@russroy
Copy link

russroy commented May 17, 2014

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
@russroy
Copy link
Author

russroy commented May 19, 2014

vagrant-triggers plugin developer acknowledges that the problem lies within that plugin and not vagrant-aws.

Closing this issue.

@russroy russroy closed this as completed May 19, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant