mirror of
https://github.com/ansible-collections/community.mysql.git
synced 2025-04-04 09:40:31 -07:00
dd7e297d50
* fix missing symlink to mysql binaries for MariaDB 11+ * update tested version of MariaDB 11.4 instead of 10.5 * add changelog fragment * [CI] add way to trigger workflow manually Useful in the case we don't modifiy any files in the paths: sections of the push event. * add version check for mariadb < 10.4.6 without mariadb* binaries * Use same concatenation method between functions to avoid future confusion I didn't notice that db_dump and db_import were different, thus I introduced a bug with the initialization of the variable cmd. This commit fixes that.
172 lines
9 KiB
Markdown
172 lines
9 KiB
Markdown
# MySQL and MariaDB collection for Ansible
|
|
[](https://github.com/ansible-collections/community.mysql/actions?query=workflow%3A"Plugins+CI") [](https://codecov.io/gh/ansible-collections/community.mysql) [](https://matrix.to/#/#mysql:ansible.com)
|
|
|
|
This collection is a part of the Ansible package.
|
|
|
|
## Our mission
|
|
|
|
The Ansible `community.mysql` collection goals are to produce and maintain simple,
|
|
flexible, and powerful open-source software for automating MySQL and MariaDB related tasks
|
|
providing good documentation for easy deployment and use.
|
|
|
|
## Code of Conduct
|
|
|
|
We follow the [Ansible Code of Conduct](https://docs.ansible.com/ansible/latest/community/code_of_conduct.html) in all our interactions within this project.
|
|
|
|
If you encounter abusive behavior violating the [Ansible Code of Conduct](https://docs.ansible.com/ansible/latest/community/code_of_conduct.html), please refer to the [policy violations](https://docs.ansible.com/ansible/latest/community/code_of_conduct.html#policy-violations) section of the Code of Conduct for information on how to raise a complaint.
|
|
|
|
## Communication
|
|
|
|
* Join the Ansible forum:
|
|
* [Get Help](https://forum.ansible.com/c/help/6): get help or help others.
|
|
* [Posts tagged with 'mysql'](https://forum.ansible.com/tag/mysql): leverage tags to narrow the scope.
|
|
* [MySQL Team](https://forum.ansible.com/g/MySQLTeam): by joining the team you will automatically get subscribed to the posts tagged with [mysql](https://forum.ansible.com/tag/mysql).
|
|
* [Social Spaces](https://forum.ansible.com/c/chat/4): gather and interact with fellow enthusiasts.
|
|
* [News & Announcements](https://forum.ansible.com/c/news/5): track project-wide announcements including social events.
|
|
|
|
* The Ansible [Bullhorn newsletter](https://docs.ansible.com/ansible/devel/community/communication.html#the-bullhorn): used to announce releases and important changes.
|
|
|
|
* Matrix chat:
|
|
* [#mysql:ansible.com](https://matrix.to/#/#mysql:ansible.com) room: questions on how to contribute to this collection.
|
|
|
|
For more information about communication, see the [Ansible communication guide](https://docs.ansible.com/ansible/devel/community/communication.html).
|
|
|
|
## Contributing
|
|
|
|
The content of this collection is made by [people](https://github.com/ansible-collections/community.mysql/blob/main/CONTRIBUTORS) just like you, a community of individuals collaborating on making the world better through developing automation software.
|
|
|
|
We are actively accepting new contributors.
|
|
|
|
Any kind of contribution is very welcome.
|
|
|
|
You don't know how to start? Refer to our [contribution guide](https://github.com/ansible-collections/community.mysql/blob/main/CONTRIBUTING.md) or ask us in the [#mysql:ansible.com room](https://matrix.to/#/#mysql:ansible.com) on [Matrix](https://docs.ansible.com/ansible/devel/community/communication.html#ansible-community-on-matrix)!
|
|
|
|
## Collection maintenance
|
|
|
|
The current maintainers (contributors with `write` or higher access) are listed in the [MAINTAINERS](https://github.com/ansible-collections/community.mysql/blob/main/MAINTAINERS) file. If you have questions or need help, feel free to mention them in the proposals.
|
|
|
|
To learn how to maintain / become a maintainer of this collection, refer to the [Maintainer guidelines](https://github.com/ansible-collections/community.mysql/blob/main/MAINTAINING.md).
|
|
|
|
It is necessary for maintainers of this collection to be subscribed to:
|
|
|
|
* The collection itself (the `Watch` button -> `All Activity` in the upper right corner of the repository's homepage).
|
|
* The "Changes Impacting Collection Contributors and Maintainers" [issue](https://github.com/ansible-collections/overview/issues/45).
|
|
|
|
They also should be subscribed to Ansible's [The Bullhorn newsletter](https://docs.ansible.com/ansible/devel/community/communication.html#the-bullhorn).
|
|
|
|
## Governance
|
|
|
|
We, [the MySQL team](https://forum.ansible.com/g/MySQLTeam), use [the forum](https://forum.ansible.com/tag/mysql) posts tagged with `mysql` for general announcements and discussions.
|
|
|
|
The process of decision making in this collection is based on discussing and finding consensus among participants.
|
|
|
|
Every voice is important and every idea is valuable. If you have something on your mind, create an issue or dedicated forum [discussion](https://forum.ansible.com/new-topic?title=topic%20title&body=topic%20body&category=project&tags=mysql) and let's discuss it!
|
|
|
|
## Included content
|
|
|
|
- **Modules**:
|
|
- [mysql_db](https://docs.ansible.com/ansible/latest/collections/community/mysql/mysql_db_module.html)
|
|
- [mysql_info](https://docs.ansible.com/ansible/latest/collections/community/mysql/mysql_info_module.html)
|
|
- [mysql_query](https://docs.ansible.com/ansible/latest/collections/community/mysql/mysql_query_module.html)
|
|
- [mysql_replication](https://docs.ansible.com/ansible/latest/collections/community/mysql/mysql_replication_module.html)
|
|
- [mysql_role](https://docs.ansible.com/ansible/latest/collections/community/mysql/mysql_role_module.html)
|
|
- [mysql_user](https://docs.ansible.com/ansible/latest/collections/community/mysql/mysql_user_module.html)
|
|
- [mysql_variables](https://docs.ansible.com/ansible/latest/collections/community/mysql/mysql_variables_module.html)
|
|
|
|
|
|
## Releases Support Timeline
|
|
|
|
We maintain each major release (1.x.y, 2.x.y, ...) for two years after the next major version is released.
|
|
|
|
Here is the table for the support timeline:
|
|
|
|
- 1.x.y: released 2020-08-17, EOL
|
|
- 2.x.y: released 2021-04-15, EOL
|
|
- 3.x.y: released 2021-12-01, current
|
|
- 4.x.y: To be released
|
|
|
|
|
|
## Tested with
|
|
|
|
### ansible-core
|
|
|
|
- stable-2.16
|
|
- stable-2.17
|
|
- stable-2.18
|
|
- current development version
|
|
|
|
### Python
|
|
|
|
- 3.8 (Unit tests only)
|
|
- 3.9 (Unit tests only)
|
|
- 3.10 (Sanity, Units and integrations tests)
|
|
- 3.11 (Unit tests only, collection version >= 3.10.0)
|
|
|
|
### Databases
|
|
|
|
For MariaDB, only Long Term releases are tested. When multiple LTS are available, we test the oldest and the newest only. Usually breaking changes introduced in the versions in between are also present in the latest version.
|
|
|
|
- mysql 5.7.40 (collection version < 3.10.0)
|
|
- mysql 8.0.31 (collection version < 3.10.0)
|
|
- mysql 8.4.1 (collection version >= 3.10.0) !!! FAILING, no support yet !!!
|
|
- mariadb:10.3.34 (collection version < 3.5.1)
|
|
- mariadb:10.4.24 (collection version >= 3.5.2, < 3.10.0)
|
|
- mariadb:10.5.18 (collection version >= 3.5.2, < 3.10.0)
|
|
- mariadb:10.5.25 (collection version >= 3.10.0, <3.13.0)
|
|
- mariadb:10.6.11 (collection version >= 3.5.2, < 3.10.0)
|
|
- mariadb:10.11.8 (collection version >= 3.10.0)
|
|
- mariadb:11.4.5 (collection version >= 3.13.0)
|
|
|
|
### Database connectors
|
|
|
|
- pymysql 0.7.11 (collection version < 3.10 and MySQL 5.7)
|
|
- pymysql 0.9.3
|
|
- pymysql 0.10.1 (for RHEL8 context)
|
|
- pymysql 1.0.2 (collection version >= 3.6.1)
|
|
- pymysql 1.1.1 (collection version >= 3.10.0)
|
|
|
|
## External requirements
|
|
|
|
The MySQL modules rely on a [PyMySQL](https://github.com/PyMySQL/PyMySQL) connector.
|
|
|
|
The `mysqlclient` connector support has been [deprecated](https://github.com/ansible-collections/community.mysql/issues/654) - use `PyMySQL` connector instead! We will stop testing against it in collection version 4.0.0 and remove the related code in 5.0.0.
|
|
|
|
## Using this collection
|
|
|
|
### Installing the Collection from Ansible Galaxy
|
|
|
|
Before using the MySQL collection, you need to install it with the Ansible Galaxy CLI:
|
|
|
|
```bash
|
|
ansible-galaxy collection install community.mysql
|
|
```
|
|
|
|
You can also include it in a `requirements.yml` file and install it via `ansible-galaxy collection install -r requirements.yml`, using the format:
|
|
|
|
```yaml
|
|
---
|
|
collections:
|
|
- name: community.mysql
|
|
```
|
|
|
|
Note that if you install the collection from Ansible Galaxy, it will not be upgraded automatically if you upgrade the Ansible package. To upgrade the collection to the latest available version, run the following command:
|
|
|
|
```bash
|
|
ansible-galaxy collection install community.mysql --upgrade
|
|
```
|
|
|
|
You can also install a specific version of the collection, for example, if you need to downgrade when something is broken in the latest version (please report an issue in this repository). Use the following syntax:
|
|
|
|
```bash
|
|
ansible-galaxy collection install community.mysql:==2.0.0
|
|
```
|
|
|
|
See [Ansible Using collections](https://docs.ansible.com/ansible/latest/user_guide/collections_using.html) for more details.
|
|
|
|
## Licensing
|
|
|
|
<!-- Include the appropriate license information here and a pointer to the full licensing details. If the collection contains modules migrated from the ansible/ansible repo, you must use the same license that existed in the ansible/ansible repo. See the GNU license example below. -->
|
|
|
|
GNU General Public License v3.0 or later.
|
|
|
|
See [LICENSE](https://www.gnu.org/licenses/gpl-3.0.txt) to see the full text.
|