schema rule unhappy about become_method from another collection

[Dunedan]

I have the feeling that I'm missing something obvious, but I can't get ansible-lint to accept a become_method from another collection for the schema[tasks] rule.

Here is a minimal example to reproduce this behavior:

- name: Show failing schema[tasks] rule
  ansible.builtin.debug:
    msg: "hello world"
  become: true
  become_method: community.general.sudosu
  become_user: someuser

When encountering this task, ansible-lint exits with the following error message:

schema[tasks]: {'name': 'Show failing schema[tasks] rule', 'ansible.builtin.debug': {'msg': 'hello world'}, 'become': True, 'become_method': 'community.general.sudosu', 'become_user': 'someuser'} is not valid under any of the given schemas
roles/test/tasks/main.yml:1  Returned errors will not include exact line numbers, but they will mention
the schema name being used as a tag, like ``schema[playbook]``,
``schema[tasks]``.

This rule is not skippable and stops further processing of the file.

If incorrect schema was picked, you might want to either:

* move the file to standard location, so its file is detected correctly.
* use ``kinds:`` option in linter config to help it pick correct file type.


Read documentation for instructions on how to ignore specific rule violations.

              Rule Violation Summary              
 count tag           profile rule associated tags 
     1 schema[tasks] basic   core                 

Failed after min profile: 1 failure(s), 0 warning(s) on 3 files

Looking at the JSON Schema for become_method, there doesn't seem to be a way to make ansible-lint happy, but there surely must be one.

What's the recommended solution for this situation?

[dlefevre]

I'm curious about this as well. I'm using become_method: containers.podman.podman_unshare and there's no way to get it validated against the tasks schema.

The only workaround I've found so far is to exclude the path of the offending yaml in .ansible-lint. However, that's kinda throwing out the baby with the bathwater.

[guppy0130]

Looks like any changes would go here (assuming the comment about generation from ansible.json still holds?):

ansible-lint/src/ansiblelint/schemas/ansible.json

Lines 43 to 65 in 4232927

	"become_method": {
	"markdownDescription": "See [become](https://docs.ansible.com/ansible/latest/user_guide/become.html)",
	"oneOf": [
	{
	"enum": [
	"sudo",
	"su",
	"pbrun",
	"pfexec",
	"runas",
	"dzdo",
	"ksu",
	"doas",
	"machinectl"
	],
	"type": "string"
	},
	{
	"$ref": "#/$defs/full-jinja"
	}
	],
	"title": "Become Method"
	},

I see become_method takes jinja though:

ansible-lint/src/ansiblelint/schemas/ansible.json

Lines 60 to 62 in 4232927

	{
	"$ref": "#/$defs/full-jinja"
	}

so something silly like

  become_method: "{{ 'ansible.netcommon.enable' }}"

will pass, but that's not great