Ansible core added a new field, cli for a single plugin.

[abadger]

Ansible core added a new field, cli to plugin documentation here:
ansible/ansible#73708

[abadger]

This should fix: ansible/ansible#74838

[felixfontein]

@abadger thanks for implementing this!

[abadger]

I've looked into the information in the cli field and I don't think that it's usable for documentation. The only thing it contains is the name of an internal variable so it has no meaning to outside users. This is different than all of the other similar fields (vars, env, ini) which specify things that are recognizable to the user and then the config subsystem has to decide how to map those to the backends which it gathers information from.

I'd almost say we need to propose a cliv2: field which makes this actually usable but afaics, this is only currently applicable to the ssh plugin and in any expansion, it could only be applicable to ansible-core plugins (because it doesn't allow the plugin to specify new command line args that ansible and ansible-playbook will then know about so a collection won't be able to use it.)

Between the latter and that the '--extra-vars' command line arg already exists for ansible and ansible-core (which lets users feed something specified on the command line to a plugin's vars: entry), this may not have even been a good feature to add. It may have been better for the ssh plugin to merge the information from config and the parsed command line args itself.

[acozine]

I would vote to roll back the YAML changes in ansible/ansible#73708 if the cli option isn't accessible to users. @bcoca what was your goal when you added it?