Am Mittwoch, 26. Oktober 2016 19:21:02 UTC+2 schrieb rup: > > We implemented this by having host files specific to an environment, so > for example, a QA host file, a Prod host file, a Dev host file, etc. Then > the groupings within the host file would be based off what they were used > for, for example: > > ... > > Then when calling the playbook, we just pull in the appropriate host file > for the environment we want to have updated. Is this what you were talking > about? >
Not exactly, however I realize that by "double-assigning" hosts in my inventory I have kind of solved my problem already. The issue is that my "second" hosts file / inventory is currently generated by Vagrant, so I need to create the appropriate groups there, also. Like i suspected the problem lies more with my use of Vagrant, rather than Ansible. Thanks for your comment! -- 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/62993481-8b07-47f2-82ec-e9dd53c6e617%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
