I think with this I am still setting every configuration related to one service in single var file so this way I am maintaining state of the service at one place and every common thing for all the services will be written in single playbook.
On Wednesday, January 21, 2015 at 10:35:28 PM UTC+5:30, Jonathan Davila wrote: > > Seems to be sort of an anti-pattern to do it this way. Referencing: > https://groups.google.com/forum/#!msg/ansible-project/CPAE8_0YXMg/Az3Etfz7mP8J > > > > It sounds like a similar issue at the end. > > > On Wednesday, January 21, 2015 at 11:48:55 AM UTC-5, Suraj wrote: >> >> Hi Folks, >> >> I am trying to create single playbook for every service we have. So here >> we need to deploy multiple roles on different service instance. >> What I want is that, I want to just define variable in different group >> vars files and depending upon that variable, playbook should run the roles >> like: >> >> if we have service A which has variable like: >> roles: >> - common >> - roleA >> >> and service B has: >> roles: >> - common >> - roleB >> >> now single playbook should run use these variables and depending upon >> value it should sun respective roles on respective service instances like: >> >> playbook.yml >> >> .... >> >> roles: >> - { role : "{{ item }}" } >> with_items: >> - roles >> >> But it is not working as I want, it give me error: >> "*ERROR: with_items is not a legal parameter at this level in an Ansible >> Playbook*" >> >> Any Ideas how can I achieve the same using conditions in playbook?? >> >> Best Wishes, >> Suraj >> > -- 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/ea09d9ce-7315-438e-9e71-c02d38976b3c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
