Thanks for your suggestions. I think my approach will be to use the template file to create the configuration only if it doesn't exist, and then use config set/rewrite to set any configuration variables that may change over the project lifetime.
Ansible 1.6 includes some more options to the redis module to make the second part easier, so I may just wait until ansible 1.6 is stable. As I said, my current approach that resets the configuration files and restarts redis on every provision appears to work, it just feels icky. Bryan > 3. Perhaps write some custom facts that get the current state of the > Redis configuration and incorporate them into the template? You > might also find Redis' CONFIG GET/SET/REWRITE commands useful. > -- > Morgan Hamill > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Ansible Project" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/ansible-project/7YEJnysAJaE/unsubscribe. > To unsubscribe from this group and all its topics, 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/1396445081-sup-3584%40al.wesleyan.edu > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CAJbEnTzDV3FoY-2TWdTjkg4aZOaA4h7NjxMgCfZHuhtf1xk_EQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
