-
Notifications
You must be signed in to change notification settings - Fork 739
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
Ansible 2.0 support #59
Conversation
The test fails because of this new behaviour: I will take a look on how to fix this. |
This can be merged after #63 |
0d99de2
to
1fc21c6
Compare
#63 is merged, so we should be good here. You could also create an additional Looks like Travis is defaulting to the newest release of Ansible at all times, which should give decent warning about breakage. |
Sounds like a really good plan! I'll add that, and maybe try it with travis, too. |
d1ba3b6
to
32f65fb
Compare
@rndmh3ro Should we test with Ansible 1.9 and Ansible 2.0? We could easily use multiple kitchen files. Within travis we can then prefix with |
I also like the approach from @conorsch where we overwrite the ansible version in yml for the specific suite. +1 for that solution |
32f65fb
to
75cbba4
Compare
This role was tested with Ansible 2.0
75cbba4
to
1b35de9
Compare
@chris-rock Something like this would do the trick:
|
Yes, I'm going to implement this. Also in travis. |
@conorsch yes, this is a very good approach! |
New release 3.0.0
This role was tested with Ansible 2.0