Try setting up one inventory for QA, another for DEV, and a third for production. You can use the same playbooks with different inventories so it'll keep the environments isolated but you'll get better consistency between each env.
On 6 July 2017 at 07:36, <[email protected]> wrote: > Hi, > > assume we would have 1000 projects in a big company and an OPS guys > tells us to copy every detail for provisioning for qa, dev and prod in one > repository. Some told arguments: > > just to clone one repository > all Unix machines require a basic setup and therefore the concrete inventory > file has to have all hosts and roles > (the intention is to maintain the host names at multiple locations) > > a) Is this the way to go or is there a better solution? > b) when a) could you please provide examples (url's) where to read? > > Kind Regards, > Thomas > > -- > 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/54c81f68-5bd5-451e-9194-e68c7ed9cac9%40googlegroups.com. > 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/CAK5eLPSQCWtSrtQOh7JSHfuNfcNMEdT7zm2bkNmvPnw6qAmfcg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
