You are not passing a config name, you are passing a group name, groups in Ansible are used for 2 things:
- a way to target hosts - a way to bulk assign variables to a host As such variables are not assigned to the group when you target it in the play, only the host, since the same host is member of 2 groups it inherits the variables from both, not just the one you target in the play. Since there is a conflict the 'last one merged wins', groups are evaluated by child/parent relationship and then by name. (in 2.4 we introduce priorities to give you fine grained control ... docs pending). For your situation, I would either use 2 different inventories, (live and dev) or key that variable via extra vars or vars_files. ---------- Brian Coca -- 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/CACVha7ePNQ1zFYhtT1MUn%3DTQyOyU5coyCG%2BkkWRCY%2BiieTjw9Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
