People using vagrant are driving things top-down through the new provisioner, so the idea of using ansible to fire against
vagrant which then calls ansible seems weird to me.  This module can still be maintained outside of core.

Documentation: Mention vars_files before the Roles section in playbooks1 chapter

New module 'set_fact' to define host facts

apt module: part rewrite of the upgrade logic

URI module -- make it support HTTP 301, 302, 303, 304, 307

While here factor out password prompting in ansible.utils

Added 'validate' feature to copy and template modules,

If sudoing and the sudo user is not root, the original file is saved as you, therefore delete that file as you.

Allow args: var to be used to pass a variable in bare, and also templated versions should also DWIM.

in new template system.

Add region support to ec2 volume module.

environment: foo

Add region parameter and changed connection code.

Fix test so that it is /bin/sh compliant (issue #2742)

The old test used syntax that appeared to be bash-specific and did not
work on platforms where /bin/sh did not point to bash.  See issue #2742
where copy to solaris hosts failed with the error:

    output: {'stdout': '', 'stderr': '/bin/sh: test: argument expected\n',
             'rc': 1}

handlers must be run once

Documentation: Links are the best kinds of instructions

Nit fix spelling of separate

Link people right to this page on Github, so they can click "edit" right there. No need for them to search for the repo, figure out that the docsite isn't a separate repo, and navigate to the given dir.

The Roles section assumes some familiarity with vars_files, which this note attempts to briefly provide.

sysctl check fails if a custom sysctl_file is given.

so remove all occurences of each host from the handlers notified by
lists