Please note the name of an ec2 tag group will be “ec2_tag_tagName_tagValue” not “tag_tagName_value”. This is likely the problem.
Using the inventory scripts on the development branch, the tag “ec2_tag_tagName” will also be available containing everything with that tag.
Also, mixing dynamic inventory sources and INI files (crossing the streams) is really only a thing on the development branch thanks to a recent patch from @svg.
So I’d definitely recommend trying on 1.7 devel if not already, it will release very soon.
3. group_vars has a file workercommon.yml which includes variables.
-
The play's pattern references tag_worker_1 (the ec2 group). However the
variables from the "workercommon" group are not available.
This is very logic, as your ec2 hosts are not member of workercommon, so
they don't get those variables.
[workercommon:children]
tag_worker_1
groups_vars for workercommon will be available. This won't work for me
because I need to compose workercommon with other groups that will not
include tag_worker_1.
Hard to see from here but my guess is you can remodel your groups, and have
an extra group to handle those differences.