"means that CommonInventory is duplicate many times. (And I can't commit symlinks to our source control)"
It sounds like you need to better arrange groups such that you can specify groups, rather than breaking them up into seperate inventories maybe. Though for larger cases or if you want something more custom, inventory scripts are useful, and if using directories, you can even do things like speak dynamically to Rackspace and EC2 and GCE all in the same call. On Wed, Jun 25, 2014 at 2:56 PM, Matt Martz <[email protected]> wrote: > I believe the recommended approach for you would be to instead use > inventory scripts. At that point, your bounds are limitless. > > http://docs.ansible.com/developing_inventory.html > > An inventory script can use mostly anything as it's data source. You just > need to write the code to handle your scenario. > > > On Wed, Jun 25, 2014 at 1:52 PM, Stuart Reynolds < > [email protected]> wrote: > >> Is there any support for specifying multiple specific inventory files. >> For example, I may have the following clusters of service machines. >> >> ProdClusterInventory >> StagingClusterInventory >> QAClusterInventory >> DevClusterInventory >> CommonClusterInventory >> >> Prod thru Dev all need to refer to database machine held in the >> CommonClusterInventory -- so naturally, I often want playbooks to refer to >> machine groups in, say ,ProdClusterInventory and CommonClusterInventory. >> >> ansible -i appears to only allow a single inventory file to be specified. >> Using -i to refer to a directory: >> >> DevCluster/ >> DevInventory >> CommonInventory >> >> means that CommonInventory is duplicate many times. (And I can't commit >> symlinks to our source control) >> >> >> Ideally (I think), I should be able to say an inventory file includes >> another. >> >> - Stuart >> >> >> -- >> 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/58c14dbe-4ee6-4b7a-96ac-373ff5984fdb%40googlegroups.com >> <https://groups.google.com/d/msgid/ansible-project/58c14dbe-4ee6-4b7a-96ac-373ff5984fdb%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Matt Martz > [email protected] > http://sivel.net/ > > -- > 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/CAD8N0v8yyD2p19kcYTfF-T5oypfUFKG9KhiVyU8zJj9zn3_p_A%40mail.gmail.com > <https://groups.google.com/d/msgid/ansible-project/CAD8N0v8yyD2p19kcYTfF-T5oypfUFKG9KhiVyU8zJj9zn3_p_A%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > 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/CA%2BnsWgzJM0a-s72x4vSX60sTKMUs9qLG5Dt1GS9_HpnXRnrObA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
