Hey Adam, I think you *could* do this with a chain of "region" variables, but that seems like it could be cumbersome. Here is a piece of code I wrote that I've been playing with: https://github.com/blueboxgroup/ursula/pull/224/files
Essentially it allows you to define some global defaults, and then overlay/augment them with the standard group_vars. I may change this to lexically read a directory for chains of defaults I care about, for instance: 01-global_defaults.yml 02-organization_defaults.yml ... then group_vars ... etc, etc. Does this help? Craig On Tuesday, January 14, 2014 2:36:15 PM UTC-5, Adam Morris wrote: > > > On Jan 14, 2014 8:01 AM, "Michael DeHaan" > <[email protected]<javascript:>> > wrote: > > > > The super easiest way to deal with things is actually to just have a > group for each type of system and then use group variables. > > > > I agree that that is an easy solution. I would do that if I could find a > way to include variable files within variable files... that way I could > have a generic RedHat file that was included in both the RedHat5 and > RedHat6 files. > > Then RedHat5 and RedHat6 groups could exist with the maximum of > reusability. > > If this facility exists then I apologise, but I couldn't find it in the > documentation. > > Adam. > -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
