Well worth looking at doing this with inventory and group_vars Chris -
ideally you want to avoid embedding lots of {% if %} stuff in templates,
because it makes it harder for people to follow what you're doing.
Make the software do the work for you...
http://docs.ansible.com/intro_inventory.html#group-variables
On Tuesday, 10 February 2015 12:51:46 UTC, Chris Short wrote:
>
> I kinda get it? Maybe I'm not presenting this correctly or largely enough.
> I need to deploy multiple configuration files (dozens) across multiple
> environments. Configurations would likely not share many values. For
> example:
>
> AppA
> |_ConfigA - 7 different option/variable pairs
> |_ConfigB - 4 different option/variable pairs
> |_ConfigC - 12 different option/variable pairs
>
> AppB
> |_ConfigD - 2 different option/variable pairs
> |_ConfigE - 17 different option/variable pairs
> |_ConfigF - 24 different option/variable pairs
>
> The list goes on and on. Also, some environments might have one
> option/variable pair where others have multiples (dev lab moving on up
> through production).
>
> Can anyone point me to an example of this? The documentation doesn't seem
> to be helping me see this on a grander scale (or maybe I'm missing
> something).
>
--
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/5530a50a-cfa6-4ae5-9d88-461e1bf2b83e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
