Had the same issue.
Here's what I did to get Boto debug working. Maybe some of these steps are
not needed, I didn't take the time to investigate more.
1) Created a ~/.boto.cfg file as you did, with the following content (I put
my AWS credentials here on purpose):
[Boto]
debug = 2
[Credentials]
aws_access_key_id = ...
aws_secret_access_key = ...
2) Made sure to *delete* ~/.aws/credentials so that Ansible picks up the
previous Boto config file
3) and the most ugly part, monkey-patched the Ansible module I wanted to
test (ec2_elb) to redirect Boto logs to a file, since I could never get the
console/stdout output to work.
On my system, the module I wanted Boto debug for was located in
/Library/Python/2.7/site-packages/ansible/modules/cloud/amazon/ec2_elb.py.
Just after the various import boto, import boto.ec2... lines, I added
boto.set_file_logger('boto', 'boto.log', level=2)
This creates the "boto.log" log file in the current directory from where
you'll run your ansible-playbook comand.
On Wednesday, May 25, 2016 at 7:59:58 PM UTC+8, Cos Bug wrote:
>
> Hi All,
>
> Is there any way to turn on boto debugging for Ansible playbooks?
>
> In user home directory I created .boto file with contents:
>
> [Boto]
> debug = 2
>
> But Ansible doesn't pick it up though the python script which invokes boto
> prints the debug messages fine.
>
> Any ideas?
>
> Regards,
> Constantin
>
--
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 ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/5a5a7445-8236-4104-b8d6-1730a1d816ad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
