Re: [ansible-project] Ansible Python API 2.0 - capture warnings

2018-04-16 Thread Suren Baskaran
Hey Guys Badly need some pointers here - as I am running out of options Fiddling with the display Utils gives me the needed verbose but to stdout and not the callbacks Thanks, Suren VB From: Suren Baskaran Sent: Friday, April 13, 2018 4:36:41 AM To: ansible

Re: [ansible-project] Ansible Python API 2.0 - capture warnings

2018-04-12 Thread Suren Baskaran
Hey Brain Appreciate some pointers here Thanks, Suren VB From: Suren Baskaran Sent: Thursday, April 12, 2018 11:52:23 AM To: ansible-project@googlegroups.com; Ansible Project Subject: Re: [ansible-project] Ansible Python API 2.0 - capture warnings Thanks for the

Re: [ansible-project] Ansible Python API 2.0 - capture warnings

2018-04-11 Thread Suren Baskaran
Thanks for the prompt response Brian Any examples or references on how to integrate the display with playbook executor callbacks ? Appreciate your response Thanks, Suren VB From: ansible-project@googlegroups.com on behalf of Brian Coca Sent: Wednesday, April

[ansible-project] Ansible Python API 2.0 - capture warnings

2018-04-11 Thread Suren Baskaran
Hello All Been circling around the Callbackbase with all possible tries , but I could not find a way till now to capture these warnings from a playbook execution with the API output [WARNING]: * Failed to parse hosts/UAT/ dictionary, got: [WARNING]: * Failed to parse /hosts/UAT/ssh_keys/dbr

[ansible-project] Ansible command-line like verbose > 3 using python API 2.0

2018-04-03 Thread Suren Baskaran
Hi So when we run a ansible playbook in command line with -vvv [ verbosity=3] we get all these below information like "Task path" , "using module" and the internals of how each hosts gets connectivity established. TASK [SHOW THE LAST 10 ALERTS ] **