community.mysql/plugins
MattMontgomeryKochava 175ad8899c When using statement based replication in a master-master configuration
there exists a race condition that can break replication when dropping a user.
Ideally one would use the "sql_log_bin: no" option to avoid this but
that is not possible on Google CloudSQL instances. Adding IF EXISTS
clause to the DROP USER statement makes it replication safe without
the need to skip logging.
2022-02-11 17:53:32 -06:00
..
doc_fragments fix typo (#190) 2021-07-09 09:17:44 +02:00
module_utils When using statement based replication in a master-master configuration 2022-02-11 17:53:32 -06:00
modules Honor the set_default_role_all parameter (#282) 2022-02-04 10:43:24 +01:00
README.md Link to latest plugin docs (not 2.9) 2020-10-11 06:10:25 +01:00

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.