{"push_id":989292392,"size":1,"distinct_size":1,"ref":"refs/heads/remote_execution_provider","head":"1a709c7cb9024d268bf42b68085b3151e4f22f5f","before":"a3666ac85fafd097cb724c7d1bba7886d951b275","commits":[{"sha":"1a709c7cb9024d268bf42b68085b3151e4f22f5f","author":{"email":"7ce40c283fd6ba485d3707dc93d14cafcc8864bf@gmail.com","name":"Daniel Lobato"},"message":"Fixes #13812 - Remote execution provider\n\nAnsible can be used as a provider for remote execution. The job\ntemplates can be Ansible playbooks that use host parameters, properties\nand ERB.\nJob templates, however, should have a 'hosts' section that just contains\n<%= @host.name %>, because a new inventory is generated per host with\nall the required variables.\nIn any case, the way it should work is:\n\nForeman sends request to proxy - including the 'hosts' it's supposed to\nrun on.\nProxy generates an inventory with the hosts and variables required\nProxy runs ansible and reports to Foreman\n\nThe reason why ansible_foreman_inventory cannot be used in this case is\nbecause it's less flexible than the 'search' field of REX, where one can\nuse the 'scoped_search' syntax to figure out what hosts to run the\nplaybook on. If we used ansible_foreman_inventory for that, we would be\nforced to run our playbooks on a set of hosts, hostgroups, organiztions\nor locations.","distinct":true,"url":"https://api.github.com/repos/dLobatog/foreman_ansible/commits/1a709c7cb9024d268bf42b68085b3151e4f22f5f"}]}