Fixes for Ansible 2.0

[x89]

No description provided.

[maschmann]

Main Problem ist: I'm not yet sure if I can incorporate the changes in a way to support both, ansible 2.0 and 1.9. Since we're using this deployment for our production system here, and are not able to update 2.0 for a while, this is somewhat... challenging ;-)

[x89]

@maschmann I tried to make sure it was backwards compatible!

There are a few more changes for things I don't use in my own production I believe, also let me update the changes because | exists is required to prevent erroring out!

[x89]

Either way you need to get it working for 2.0 now it's the main release ;)

Let me know if I can help!

[maschmann]

Hi,
I first had to resolve the folder structure problems for the change from sf 2.8 -> 3.x
Now I'll need to build a test environment for ansible 2 here, since we are not able to use it yet, environment-wise. That's also true for lots of my colleagues, since Ansible 2 has some breaking changes and early adopting is not the common path when using Provisioning in a production environment :-)

[maschmann]

I've had a look into the include changes: It is possible to do this in the way you've implemented id, but just checking the included task variable to be not empty seems to be a bad idea, since it breaks if e.g. the null value handling of ansible changes. Would be better to use a file stat instead?

//edit
As far as I've seen there's no jinja "exists" filter. This then has to be done with file stat.
I'll add the stat in 00-facts and set a include file variable to True/False if file is present.
btw: good idea to name the includes and add a "when". Overread that the conditional inclusion works with tasks - thought it didn't work, since playbooks couldn't be included conditionally with <2.0