Guillaume Coré

same here: ``` Traceback (most recent call last): File "/usr/bin/ansible-playbook", line 324, in sys.exit(main(sys.argv[1:])) File "/usr/bin/ansible-playbook", line 210, in main force_handlers=options.force_handlers, File "/usr/lib/python2.7/site-packages/ansible/playbook/__init__.py", line 181, in __init__ ansible.callbacks.load_callback_plugins() File "/usr/lib/python2.7/site-packages/ansible/callbacks.py",...

i could reproduce this issue. it's different from #23955 though as i cannot reproduce 23955 with directory, only symlink dirs seem to have the issue.

Shouldn't `--check` still mimic normal behavior, with or without `follow: yes` ?

This is a common role, can you please explain why it is needed, what feature it gives, what usecase it serves, etc. Can we have documentation along in the readme...

Now that we have an easy way to deploy using python virtualenv, fixing the deprecation warning should not be an issue anymore. I'm happy to move this forward and accept...

Not necessarly. We can deal with it in ansible ```yaml - when: ansible_version.full is version_compare('2.9', '>=') include_tasks: # TODO: remove when not needed anymore - when: ansible_version.full is version_compare('2.9', '

Oh, i was only talking about ec2_ami_facts, as this issue is for that specifically

I agree that for the rest, and fixing all the deprecation warnings is not something we're going to tackle in one change

i forgot to add a comment here: i tested ec2_ami_info with the version that is on our deployer server, and it just produces an error.

@tosin2013 any update on this Pull Request ?