You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This may supersede #7 (I'm not extremely familiar with Ansible plugins yet).
The integration test playbook mentions an action plugin which is a necessary prerequisite for using the inventory connection details as the MikroTik API connection details.
What is necessary for this plugin?
The text was updated successfully, but these errors were encountered:
Nearly all ansible modules that work by connecting to an API (especially an HTTP API) do not do so through a new connection type (or any other plugin). They do so by defining variables which are consumed by the module itself. This also has the requirement that the node that you're connecting to is technically localhost.
I'm not entirely against create a plugin to manage the connection, but we should do a more thorough survey of current and future Ansible network modules to determine what is recommended.
In the meantime, there are definitely some lower hanging fruit we could do to get things much more performant (like #7)
This may supersede #7 (I'm not extremely familiar with Ansible plugins yet).
The integration test playbook mentions an action plugin which is a necessary prerequisite for using the inventory connection details as the MikroTik API connection details.
What is necessary for this plugin?
The text was updated successfully, but these errors were encountered: