Ok. So what are my options here? I cannot be the only person with a situation like this. Diverging OS baseline installs is one of the reasons ansible is used after all? Is there not any workaround?
On Wednesday, 12 February 2014 12:57:54 UTC, Michael DeHaan wrote: > > Not currently. > > Patches to add it as an inventory variable would be accepted (just apply > to any group you need), but I'm not sure it really belongs as a playbook > keyword. > > > On Wed, Feb 12, 2014 at 7:53 AM, Makimoto Marakatti > <maki...@gmail.com<javascript:> > > wrote: > >> Is there a way then to set this in a playbook at runtime? >> >> >> On Wednesday, 12 February 2014 12:39:02 UTC, Brian Coca wrote: >>> >>> this is not currently configurable by host, just the ansible.cfg setting >>> and the environment variable ANSIBLE_REMOTE_TEMP. >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Ansible Project" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to ansible-proje...@googlegroups.com <javascript:>. >> To post to this group, send email to ansible...@googlegroups.com<javascript:> >> . >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
