Public Ansible Project Meeting Agenda - September 2020

[samdoran]

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, leave that as well.

See https://github.com/ansible/community/blob/master/meetings/README.md for the schedule

Once an item has been discussed it should get checked off.

If you just want reviewers for your contribution try the #ansible-devel irc channel on freenode.

[samdoran]

• Discuss changes to the module/plugin deprecation documentation

Somewhat related to ansible/ansible#71459. That issue mainly brought to light the fact that the documentation should be updated since ANSIBLE_METADATA is no longer a thing. What should the recommended deprecation process be fore modules/plugins in the new collections-based world?

[felixfontein]

@samdoran deprecation of plugins/modules is done by deprecating them both in the module docs and in meta/runtime.yml. For modules, this is already validated by validate-modules.

[felixfontein]

• Reduce ignored module sanity tests ansible#70319

[nitzmahone]

• Should we kill ansible-galaxy login? Discussion at reimplement ansible-galaxy login with OAuth Device Flow ansible#71628

[felixfontein]

• ansible-test: improve version number validation, validate some semantic versioning properties ansible#71679
• Add deprecation collection name to plugin options ansible#71735

[felixfontein]

• Extend validate-modules to also validate plugins ansible#71734 Extend validate-modules to also validate plugins. Questions to discuss for standardizing plugin schemas:
  • what's with name: next to description: in option descriptions? (see default_callback docs_fragment for extensive usage) (validate-modules for plugins: what's with name: next to description: in option descriptions? ansible#71792)
  • which plugin types must have / can have / cannot have examples? (validate-modules for plugins: which plugin types must have / can have / cannot have examples? ansible#71793)
  • author: required with same conditions as for modules, or optional, or other conditions? (validate-modules for plugins: author: required with same conditions as for modules, or optional, or other conditions? ansible#71794)
  • <plugin_type>: <name> vs. plugin_type: <plugin_type> and name: <name> (validate-modules for plugins: <plugin_type>: <name> vs. plugin_type: <plugin_type> and name: <name> ansible#71795)
  • option type: should long forms boolean, string, integer etc. be allowed? (validate-modules for plugins: option type: should long forms boolean, string, integer etc. be allowed? ansible#71796)
  • return value type: required or not for plugins? (validate-modules for plugins: return value type:, elements: and returned: required or not for plugins? ansible#71797)
  • for callback plugins, type vs. callback_type (validate-modules for plugins: for callback plugins, type vs. callback_type ansible#71798)

[felixfontein]

• Validate plugin option type 'dict' / 'dictionary' ansible#71928 add validation for type: dict for plugin options

[felixfontein]

• should ansible -version etc. also show the Ansible version? (For example, antsibull-build could add a Python module to the pypi package called ansible_collections/ansible_version.py, which if found would provide the Ansible version)

[bcoca]

Meeting ended Tue Sep 29 20:10:36 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot .
Minutes: https://meetbot.fedoraproject.org/ansible-meeting/2020-09-29/ansbile_core_irc_public_meeting.2020-09-29-18.58.html
Minutes (text): https://meetbot.fedoraproject.org/ansible-meeting/2020-09-29/ansbile_core_irc_public_meeting.2020-09-29-18.58.txt
Log: https://meetbot.fedoraproject.org/ansible-meeting/2020-09-29/ansbile_core_irc_public_meeting.2020-09-29-18.58.log.html