ansible-collections/community.mysql
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.mysql.git synced 2025-04-06 10:40:36 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
community.mysql/plugins
History
Laurent Indermühle a5f3296d73
mysql_info - Add connector_name and connector_version to returned value (#497) 
* Add methods to retrieve connector name and version
* Document that mysqlclient is also named MySQLdb
* Document version_added
* Add connector name and version in the returned block
* Cut condition to display any name that is return

In case of MySQLdb is renamed in mysqlclient. In that case, the
integration tests will catch this the day we update the connector
version.

Co-authored-by: Andrew Klychkov <aaklychkov@mail.ru>
2023-01-30 13:35:24 +01:00
..
doc_fragments * add socket option suggestion in documentation (#437) 2022-10-04 11:08:59 +02:00
module_utils mysql_info - Add connector_name and connector_version to returned value (#497) 2023-01-30 13:35:24 +01:00
modules mysql_info - Add connector_name and connector_version to returned value (#497) 2023-01-30 13:35:24 +01:00
README.md Link to latest plugin docs (not 2.9) 2020-10-11 06:10:25 +01:00

README.md

Collections Plugins Directory

This directory can be used to ship various plugins inside an Ansible collection. Each plugin is placed in a folder that is named after the type of plugin it is in. It can also include the module_utils and modules directory that would contain module utils and modules respectively.

Here is an example directory of the majority of plugins currently supported by Ansible:

└── plugins
    ├── action
    ├── become
    ├── cache
    ├── callback
    ├── cliconf
    ├── connection
    ├── filter
    ├── httpapi
    ├── inventory
    ├── lookup
    ├── module_utils
    ├── modules
    ├── netconf
    ├── shell
    ├── strategy
    ├── terminal
    ├── test
    └── vars

A full list of plugin types can be found at Working With Plugins.