Guy, It looks like the specific case you have of filtering based on a given tag can be solved without having several inventories.
If you use the `constructed` part of inventory plugins, https://docs.ansible.com/ansible/2.7/plugins/inventory/constructed.html which lets you do all kinds of advanced grouping based on properties such as tags. Also, here's an issue you can watch which is related to allowing importing w/ vars. It doesn't extend to config, but would be the same principal. On Tuesday, October 16, 2018 at 3:19:31 PM UTC-4, Guy Knights wrote: > > I'm experimenting with the new AWS_EC2 plugin and have been wondering if > there's a way to streamline the file as we have separate inventory folders > for dev, demo and prod. Is there a way to do something like and 'include' > for the bulk of the YAML file content and just have the different > environment filters in each inventory's specific file? eg. something like > this: > > Central file (central.aws_ec2.yml): > plugin: aws_ec2 > regions: > - us-east-1 > - us-east-1 > - us-west-1 > - us-west-2 > - ap-southeast-2 > filters: > instance-state-name: running > strict_permissions: False > hostnames: > - tag:Name > - private-ip-address > strict: False > keyed_groups: > - prefix: '' > separator: '' > key: tags.Type > > Demo inventory file (demo.aws_ec2.yml): > include: central.aws_ec2.yml > filters: > tag:Environment: demo > > Thanks, > Guy > -- 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/5be0ede7-229b-4af5-9fb9-01810fe25511%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
