7 commits

Author	SHA1	Message	Date
Matthew Johnson	0841ed4796	change method of obtaining hostname to match ansible/library/setup	2012-10-12 07:55:22 -07:00
Matthew Johnson	2b24131baa	fetch the git repo before trying to find a playbook	2012-10-12 07:55:22 -07:00
Stephen Fromm	788e11f1db	Merge commits from copperlight's branch ansible-pull_playbook_parameter branch ... Merged commits: 3cd25b5 and ed9fc76. Some massaging of changes applied.	2012-10-12 07:55:22 -07:00
Michael DeHaan	faed4b5a33	whitespace + remove deprecated YAML parser (migration script lives in examples/scripts and warning was added ... in 0.6 release)	2012-08-06 20:07:02 -04:00
Michael DeHaan	a33320d03d	Add some comments to ansible-pull and the example playbook	2012-05-01 23:22:23 -04:00
Stephen Fromm	84c9caa805	Simplify ansible-pull to just invoke ansible and ansible-playbook ... This eliminates the creation of runner and playbook instances and just invokes the processes ansible and ansible-playbook.	2012-05-02 09:51:19 -07:00
Stephen Fromm	672794f586	Add ansible-pull ... A first stab at a pull-based model for ansible. This does two things: 1. Invoke the git module via Runner to set up a git repository on the localhost. It sets up Runner to use transport='local' and forces the inventory to just 'localhost'. 2. Run any playbooks provided. By default, this wants to run the playbook local.yml. This also sets transport='local' and sets the host_list to a list: localhost, fqdn, and hostname. The reason for setting the host_list and not using override_hosts is because there may be plays in the playbook that are not meant for a specific host. That is, if the git repository is for the entire site and not host-specific, you don't want to override hosts and apply all plays to any given host. This has the downside of potentially running a play three times if the play is defined for 'hosts: all'.	2012-05-02 09:51:19 -07:00