-
Notifications
You must be signed in to change notification settings - Fork 47
Port to Ansible 2 #13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Added new file `datadog_callback_ansbile2.py` which is a copy of `datadog_callback.py` modified to work with Ansible 2. This commit is a quick attempt to maintain Ansible 2 compatibility. The V1 version has not been modified at all, and there has been no attempt to normalize the interaction with DataDog between the two versions - a big DRY violation. However, Ansible 2 works and refactoring can be done as needed/desired. Modification began with following porting guidance: https://docs.ansible.com/ansible/porting_guide_2.0.html Minor other adjustments were maded following examples: https://github.com/ansible/ansible/tree/devel/lib/ansible/plugins/callback
|
Hi @willmore @irabinovitch - having a bit of trouble with this on our buildservers, we're seeing and Any ideas as to how I can even start to debug this? |
|
Thanks @willmore , this was very helpful. I added a few things for my personal enjoyment:
If anyone wants these, here is some code.... exit if ansible < 2 : Change remote_user to shell_user: |
|
any update on this? almost 2 months have past and ansible 2 is gaining popularity |
|
possible duplicate of #11 ? |
|
@olivielpeau happy to be of help. Thanks for adding the Ansible 2 support! |
|
@joffotron i'm having a similar issue, opened a different ticket: #18 |
Added new file
datadog_callback_ansbile2.pywhich is a copy ofdatadog_callback.pymodified to work with Ansible 2.This commit is a quick attempt to maintain Ansible 2 compatibility.
The V1 version has not been modified at all, and there has been no attempt
to normalize the interaction with DataDog between the two versions -
a big DRY violation. However, Ansible 2 works and refactoring can be done as
needed/desired.
Modification began with following porting guidance:
https://docs.ansible.com/ansible/porting_guide_2.0.html
Minor other adjustments were maded following examples:
https://github.com/ansible/ansible/tree/devel/lib/ansible/plugins/callback