JM> I was just trying to work out in what situation would you want to have
JM> the inventory level group/host vars at a lower precedence than the
JM> playbook level group/host vars. It doesn't really fit with the way we
JM> are doing things.
My guess is that the expectation is that you'd typically have one
inventory, which is very consistent, but lots of playbooks, some of which
might want to do things differently. Having a playbook that's generally
consistent, but can be overridden by inventory, seems to me like a less
common use case, but of course if it's the one you've got then it's the
one you care about. :^)
You mentioned that you
struggle with default values that don't aren't defined in a role. I
appreciate that that is the preferred approach but this would mean that
we would have to include the role default everywhere we use it.
I'm not sure what you mean by "have to include the role default". If you
use the role, you get the role default, so could you maybe get what you
want here by just moving the contents of the playbook into a role?
-Josh (j...@care.com)
This email is intended for the person(s) to whom it is addressed and may
contain information that is PRIVILEGED or CONFIDENTIAL. Any unauthorized use,
distribution, copying, or disclosure by any person other than the addressee(s)
is strictly prohibited. If you have received this email in error, please notify
the sender immediately by return email and delete the message and any
attachments from your system.
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/22056.59260.740480.707540%40gargle.gargle.HOWL.
For more options, visit https://groups.google.com/d/optout.
