Okay, that makes sense. In that scenario, I assume that deploy.yml just specifies hosts: all which would pick up everything in that inventory file, right?
Thanks! On Wednesday, October 7, 2015 at 10:08:08 AM UTC-4, J Hawkesworth wrote: > > The value for hosts in the playbook can be a group of hosts (defined in > your inventory). > > I'd suggest setting up different inventory files for each environment then > you can run > > ansible-playbook -i /etc/ansible/dev-inventory deploy.yml > or > ansible-playbook -i /etc/ansible/staging-inventory deploy.yml > > Jon > > On Wednesday, October 7, 2015 at 2:53:50 PM UTC+1, Rob Wilkerson wrote: >> >> I'm tipping my toe in the Ansible pool via a simple project deployment >> script. I have 3 environments (the usual dev, staging, production) and the >> deployment is exactly the same for each. In every example I've seen so far, >> the `hosts` are hard coded in the playbook. What I'd like to do is create a >> single `deploy.yml` file and specify the `hosts` value when I call it. >> Otherwise, at least in my limited understanding so far, we'll have to >> either modify the playbook every time we want to run a deployment against >> one of our environments. >> >> I've seen something like this: >> >> $ ansible deploy.yml -e "hosts=development" >> >> where, in `deploy.yml`, we have `hosts: $hosts`, but that feels >> ham-fisted. >> >> Is this the recommended/best approach? Should I be structuring things >> differently? >> > -- 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/682ec3c8-2aac-46e7-89bf-5ed35491ab8f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
