For larger environment that seems a bit unwieldy; I am wondering what would 
be the best practice here?  E.g. are people running this sort of playbook 
automatically every x minutes and then use the cache facts?


On Tuesday, July 19, 2016 at 7:40:45 AM UTC-4, Alexey Vazhnov wrote:
>
> I know only «all_instances = False» (by default) in ec2.ini, to exclude 
> stopped.
> Unreachable hosts will be skipped by Ansible, but error messages will be 
> displayed.
>
> On Tuesday, July 19, 2016 at 3:59:48 PM UTC+5, Anthony Cheng wrote:
>>
>> I want to use the ec2_facts module to gather info, e.g.
>>
>> - hosts: all
>>   gather_facts: false
>>   become: no
>>   tasks:
>>   - name: Get instance ec2 facts
>>     action: ec2_facts
>>     register: ec2_facts
>>
>>
>> Is there a way to filter out the SSH unreachable (maybe not on first run) 
>> but maybe give them a specific tag; so check for error message and then I 
>> can tag those ec2 instance to filter them out next run?
>>
>

-- 
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/f629318f-fdf4-4a39-a4eb-3abc03a28617%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to