Yes, we have no intention of ever removing that feature, and this is a fairly normal use-case. The only other option would be to somehow fold the "static" information into your dynamic script somehow, but if you can't do that then there's nothing wrong with the way you're doing it.
On Mon, Jun 2, 2014 at 11:06 AM, Hagai Kariti <[email protected]> wrote: > Hi all. > > We're using a mix of dynamic and static inventories: the dynamic one for > updated host and hostgroups and the static one for group relations and the > occasional static host. > Is this the "proper" way to handle this usecase? Is there a better way > that doesn't require a static inventory file? And maybe more importantly, > is the inventory dir feature going to stay in Ansible? > > Thanks a lot. > > -- > 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/6f484418-3bd9-49eb-92e5-fe90079a1b3d%40googlegroups.com > <https://groups.google.com/d/msgid/ansible-project/6f484418-3bd9-49eb-92e5-fe90079a1b3d%40googlegroups.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/CAMFyvFhOS_XUm-NjKOGoXcVHAUq_G7zQx2MDcmKbYac9BH77Yw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
