On 2016-03-20 12:18, Naren wrote:
> Environment variable kind of solution is good as long as I call my
> playbooks from console. But when it comes to automation by integrating with
> external systems; the inventory generator/builder should be good enough to
> pull inventory artifacts from database, REST APIs,...
>
> All I need is something like
>
> ansible-playbook -i dynamicInventory.py --script-args "location=chennai
> region=south" my_playbook.yml
>
> here '--script-args' helps dyamicInventory.py program to pull inventory
> artifacts for specified location and region from some datastore
What aspect of automation keeps you from setting environment variables?
Where is the difference between calling from console and calling from a
script?
E.g.,
SCRIPTARGS="location=chennai region=south" bash -c 'ansible-playbook -i
dynamicInventory.py my_playbook.yml'
When you evaluate SCRIPTARGS inside dynamicInventory.py I don't see
where the difference is compared to your "--script-args" -- apart from
the syntax.
Regards,
Benjamin
--
FSU Jena | JULIELab.de/Staff/Benjamin+Redling.html
vox: +49 3641 9 44323 | fax: +49 3641 9 44321