fix: replace deprecated community.general.yaml callback plugin

[Normo]

Replace the removed community.general.yaml callback with the result_format option in ansible.builtin.default callback plugin.

The community.general.yaml callback plugin has been removed in community.general 12.0.0. The replacement is to use result_format=yaml with the default callback plugin from ansible-core 2.13+.

[schurzi]

I think this is a good idea. This however breaks our compatability with EL8 distros. Most of them are still in support, so I'd not like to drop that. Can you try adding the dependency to the current version of community.general in the collection requirements?

[rndmh3ro]

This however breaks our compatability with EL8 distros

Yeah, RHEL is still supported for 3.5 more years. So let's try to support that.

[schurzi]

I think we can make this futureproof by forcing a higher version instead. I found no deprecation of EL8 support for community.general.

Suggested change

	community.general: '>=1.0.0,<12.0.0'
	community.general: '>=12.0.0'

[Normo]

I'm confused now. We seem to be stuck between two incompatible requirements.

If we use community.general: '>=12.0.0':

• Future-proof, users get the latest community.general
• Must switch to result_format: yaml in molecule.yml
• But this breaks the EL8 support (get community.general <12.0.0 with yaml callback)

If we use community.general: '<12.0.0':

• Maintains EL8 support
• Keep callbacks_enabled: profile_tasks, timer, yaml in molecule.yml
• BUT locks ALL users to outdated community.general

Or is there another approach I'm missing?

[Normo]

Another option: Removing the yaml callback entirely:

callbacks_enabled: profile_tasks, timer

This would work on all distros without version pinning on community.general, but we lose pretty YAML-formatted output in test logs.

[schurzi]

• But this breaks the EL8 support

This is not correct and the source of your confusion. We currently declare a dependency on version 1.0.0, this version does not support the new way of things, because the new Ansible version already ships the current community.general version everything works. The older Ansible version from EL8 does include an older community.general version, that satisfies our collection requirements, but does not have the feature. When we declare a explicit dependency to the current community.general version, Ansible will update the community.general collection on the older EL8 targets to a compatible version.

[schurzi]

... which is also not correct from my side ... version 12.0.0 declares a dependency to Ansible >2.17 ... which is not possible on EL8 :D
https://galaxy.ansible.com/api/v3/plugin/ansible/content/published/collections/index/community/general/versions/

{
  "version": "12.0.0",
  "href": "/api/v3/plugin/ansible/content/published/collections/index/community/general/versions/12.0.0/",
  "created_at": "2025-11-03T18:41:29.965355Z",
  "updated_at": "2025-11-03T18:41:30.188202Z",
  "requires_ansible": ">=2.17.0",
  "marks": []
},