Agenda for Public Core Meeting - 2016-10-11 19:00 UTC

[gundalow]

Please leave a comment regarding any agenda item you wish to discuss. If you don't show up for the meeting, your item will be skipped.

If your IRC nick is different from your GitHub username, add that as well.

When closing this ticket please create the next one with label meeting_agenda

[mscherer]

Would like to discuss ansible/ansible-modules-core#4617 . While that's not my patch, I kinda reached the same conclusion (and proposed a smilar workaround), so if @dagwieers is not here, I can discuss it too (provided I am pinged on irc)

[dagwieers]

@mscherer If this solution is ok, we might want to look at apt (and other modules) in the same situation. Both returning a proper error msg= as well as a non-zero rc= is a must when doing fail_json and having with-loops.

I don't mind doing the leg-work if it is deemed the right way to go. (See discussions referred to in ansible/ansible-modules-core#4617)

Another option might be to have fail_json() return a non-zero rc value for with-loops by default (if none is provided).

[abadger]

Do we want to remove paramiko from the setup.py install_requires (it creates a runtime dependency on paramiko): ansible/ansible#17982

[abadger]

What do we want to do about ansible_managed and idempotence: ansible/ansible#17947

Possibilities:

• Remove ansible_managed and have users create it in their inventories (need a documented recipe for all of the fields if so... It looks like that's actually a bit tricky...)
• Change the meaning of two fields (file and host) and then use a string that only uses those.
• Use a static string because none of the fields can be used idempotently in a multi-admin setting.

[abadger]

Unresolved from last time: ansible/ansible#17768 Do we want to change the release process in the ways documented there?

[jctanner]

This agenda was covered today.