vagrant/test/unit/plugins/commands
Mitchell Hashimoto 5903bfb3c6 commands/push: validate configuration
/cc @sethvargo - Some weirdness here but overall should work fine. I'm
not sure if there was a GH issue this should be attached to or close. To
explain:

We just use the first machine with the default provider. A
Vagrant::Environment guarantees there is at least one machine, so
`env.machine_names.first` will always work. And we can just use the
default provider because we don't really care. Finally, it can be any
old machine we pass in because we just want the "global" config to
validate and there is no way to say "don't validate machine-specific
configs", so we might as well just pick the first machine to validate.
2015-01-04 15:43:30 -08:00
..
box/command Fix failing test 2014-08-29 11:26:09 -07:00
global-status core: Use the MachineIndex#vagrant_env method 2014-04-21 13:54:31 -07:00
list-commands Convert specs to RSpec 2.14.8 syntax with Transpec 2014-03-14 12:02:07 -03:00
login stub_env is a real helper now :) 2014-12-15 01:29:58 -05:00
plugin/action Convert specs to RSpec 2.14.8 syntax with Transpec 2014-03-14 12:02:07 -03:00
push commands/push: validate configuration 2015-01-04 15:43:30 -08:00
ssh_config Change symbols inside hashes to 1.9 JSON-like syntax 2014-05-22 12:35:12 -04:00