On Saturday, June 13, 2015 at 11:53:32 PM UTC+5:30, Brian Coca wrote: > > I used to just make them templates, keep the file in native format > and only template out the options that vary per my different > classifications (stage, location, purpose). >
I have found (in my very short time with ansible, but informed by years of creating templates in chef) that all the context I need is already abstracted in the playbook, so creating the configuration directly in the play (with substitution) and passing the final config to the role yields the most flexibility. By that I mean the role did not have decide up front what bits the config I might and and might want to parameterize. Also, some configs are soooo big, with so much optional stuff it seems best to leave declaring the config to the playbook. -- 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/ba37de24-bde3-4a08-a174-d284622ef08b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
