I'm not sure if i'm understanding correctly, in any case, any plugin
can use the built in configuration, it does not only apply to shipped
Ansible plugins.
https://docs.ansible.com/ansible/devel/dev_guide/developing_plugins.html#plugin-configuration-documentation-standards
Currently, connection
Based on my understanding, options are done at the Ansible level, e.g.
parameters for the default ssh transport are configured in the Playbook
context [1], so I do not think I could just add further configuration
options (say "foobar") for my own transport, because apparently those
things come
A variable is a variable, by the time the plugin gets it the origin is
not discernible. So using the current pulgin config system you just
need to either add an option that uses that variable as a config
source or if you are using it for an existing option, add it there.
myoption:
Hi All,
I am working on a custom connection plugin based on -- (99% the same) --
the built-in SSH connection type [1], which would need to take some
configuration from playbook variables.
Unlike the standard SSH plugin, this would use custom playbook variable
names, hence I cannot use the
