1)
I found out today that variables for individual hosts (like vars_files) data weren't available in the "hostvars" variable, which is how you get to one host's variables from another host. I already fixed this
2)
I told someone you can use Jinja2 syntax outside of templates. You can't. This means that if you want to access the variable for another host that contains periods in it, or if the variable has periods in it, you need to do it in a template, since the simple replacements don't work.
Example of what works in a template but is not legal syntax in a playbook: {{ hostvars["asdf.example.com"]["myvar" }}
Why? $hostvars.asdf.example.com.myvar is ambigious, more or less. I am not sure if we want to enable Jinja2 in playbooks again or not. But I'm thinking we should if it's not terribly slow. If this interests you, this would be an easy thing to try and benchmark.
3)
Someone wanted to iterate over a list of structured data (hashes) using with_items. Turns out you can't do that yet, patches are welcome
4)
Someone this AM fixed it so that group_vars works even if the length of your vars_files section is 0.
5)
I fixed an issue where all host groups were not being loaded using the "group_vars" system -- namely, parent groups. They now load in depth order
6)
I have made it such that ssh arguments can be set in the config file.
7)
I noticed that if you are using ./hacking/test-module, you'll be pretty confused if you have a config file. However, most people won't, thinking of just adding a warning or something, workaround would be to just temporarily set ANSIBLE_CONFIG to some path where there is no config file if you really wanted to have an installed copy and a git copy or whatever. I honestly like the config file a lot, so I'm just modifying my config file to point it's library path at my local install, and in which case it's just a matter of setting path. We have a weird mix of RPM users and source users, so I don't think we can just do one or the other, but it's a little fuzzy mentioning both in the docs. I will
probably just start mentioning the config file, since it lets people review and think about the settings.
8)
There is no point 8.
--Michael