haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
vagrant/plugins
History
Seth Vargo 214a79e057 Pushes are hashed by name, not strategy. 
@mitchellh this is a partial revert of 84ae22e. It took me a little bit
to figure out why this broke everything, but then I finally realized it.

84ae22e changes the finalize! function to lookup pushes by strategy
type, but pushes are keyed by push strategy name. In other words, given:

    config.push.define("foo", strategy: "bar")

the `push_configs` has will look like:


    { :foo => [:bar, #<PushConfig>] }

This is important, because if we key by strategy, the user cannot 
specify the same push strategy more than once:

    config.push.define("foo", strategy: "bar")
    config.push.define("zip", strategy: "bar")

If we keyed off of the strategy, this would be impossible.
 		2014-12-14 23:32:32 -05:00
..
commands commands/login: append access token to vagrantcloud => atlas URLs 2014-12-12 14:53:05 -08:00
communicators communicators/ssh: insert random key, remove insecure key 2014-10-24 09:58:18 -07:00
guests Fix line breaks 2014-12-13 21:08:31 +01:00
hosts hosts/bad: escape regexp properly [GH-4922] 2014-12-10 09:16:45 -08:00
kernel_v1 Change symbols inside hashes to 1.9 JSON-like syntax 2014-05-22 12:35:12 -04:00
kernel_v2 Pushes are hashed by name, not strategy. 2014-12-14 23:32:32 -05:00
providers providers/docker: fix support of agent forwarding 2014-12-07 11:02:50 +01:00
provisioners provisioners/ansible: use Docker proxy when needed 2014-12-08 21:43:21 +01:00
pushes kernel/v2: fix push strategy config lookup 2014-12-12 01:36:39 -08:00
synced_folders Merge pull request #4619 from dlundgren/master 2014-10-23 09:21:20 -07:00
README.md Add README to plugin directory 2012-04-18 17:48:06 -07:00

README.md

Vagrant Core Plugins

These are plugins that ship with Vagrant. Vagrant core uses its own plugin system to power a lot of the core pieces that ship with Vagrant. Each plugin will have its own README which explains its specific role.