support multiple extra_vars in ansible

[luto]

Vagrant version

Vagrant 2.0.0

Expected behavior

Ansible will happily accept multiple --extra-vars arguments:

[luto@luto dir]$ ansible --extra-vars 'a=43' --extra-vars 'b=42' -m debug -a var=b all
asteroid | SUCCESS => {
    "b": "42"
}

ansible.extra_vars is currently only able to accept a single filename or a single hash. Are you interested in changing this in a backwards compatible way, so ansible.extra_vars accepts a filename, a hash or a list of either? I'd be happy to prepare a PR.

This would enable Ansible users to overwrite values given in a file easily. It's also possible to split up variables into a set that is applicable always, and a set that is applicable for a specific provider or box.

[gildegoma]

@luto Thank you for reporting this change request. I am not sure yet, how valuable this addition would be, but I understand the idea and would like to gather more user feedbacks before going forward.

For the moment, some handy variants are possible:

• use the raw_argument option to pass additional extra-vars
• use group or host variables (defined via Vagrantfile, or via Ansible variable files)

[samiam]

👍

The cynic in me is bursting, but I'll show great restraint and simply add that I support @luto's idea. It would be useful if Vagrant handled multiple extra_vars like ansible does.

[jogipraveen]

I too like the @luto idea. It would be more handy to test the things as like Ansible does.

[troy-jacobson]

I would vote for this as well. I would like to have default variables in source control and a local file that contains developer specific values.

[spatterIight]

this would be really useful

[SeboCode]

raw_arguments is a viable workaround, but a first class solution would definitely be appreciated. Especially when working with ansible-vault, where you want to define secrets in an encrypted variable file and none-critical ones in a publicly accessible file to simplify development.