Install the MySQL client and/or server
Find a file
2018-12-06 10:52:47 +00:00
mysql Apparmor support 2018-12-06 10:52:47 +00:00
scripts Fix trailing whitespaces. 2015-10-05 21:44:20 +02:00
.gitignore Initial configuration of automated tests 2016-10-29 10:41:23 -03:00
.kitchen.docker.yml Initial configuration of automated tests 2016-10-29 10:41:23 -03:00
.kitchen.yml Update testing environment 2018-09-06 09:36:37 -03:00
.travis.yml Update testing environment 2018-09-06 09:36:37 -03:00
FORMULA Adding CentOS to os in FORMULA 2015-07-09 09:31:55 -04:00
Gemfile Initial configuration of automated tests 2016-10-29 10:41:23 -03:00
import_users.py import_users: PEP8, allow optional password via -p flag. Fix an issue 2015-03-19 14:34:27 -07:00
LICENSE Update LICENSING year 2015-03-20 20:05:42 -04:00
pillar.example Updated example pillar name overrides to match new keys 2018-11-01 16:19:46 -06:00
Rakefile Initial configuration of automated tests 2016-10-29 10:41:23 -03:00
README.rst Explain config file management state in README. 2018-11-15 14:34:26 +01:00

mysql

Install the MySQL client and/or server on Linux and MacOS.

Available states

mysql

Meta-state including all server packages in correct order. This meta-state does not include mysql.remove_test_database.

mysql.macos

Install "MySQL Community Server", "MySQL Workbench", and other related mysql products on MacOS (and create Desktop shortcuts).

mysql.macos.remove ----------------

Remove "MySQL Community Server", "MySQL Workbench", and any other enabled products from MacOS.

mysql.client

Install the MySQL client package on Linux.

mysql.server

Install the MySQL server package and start the service.

Debian OS family supports setting MySQL root password during install via debconf.

Note

If no root password is provided in the pillar, a random one will be created. Because Hydrogen doesn't have easy access to a random function (test.rand_str isn't introduced until Helium), instead, we use the not-at-all random grains.server_id. As this is cryptographically insecure, future formula versions should use the newly available random.get_str method.

mysql.server_checks

Enforces a root password to be set.

mysql.disabled

Ensure that the MySQL service is not running.

mysql.database

Create and manage MySQL databases.

mysql.python

Install mysql python bindings.

mysql.user

Create and manage MySQL database users with definable GRANT privileges.

The state accepts MySQL hashed passwords or clear text. Hashed password have priority.

Note

See the salt.states.mysql_user docs for additional information on configuring hashed passwords.

Make sure to quote the passwords in the pillar so YAML doesn't throw an exception.

mysql.remove_test_database

Warning

Do not use this state if your MySQL instance has a database in use called test. If you do, it will be irrevocably removed!

Remove the database called test, normally created as part of a default MySQL installation. This state is not included as part of the meta-state above as this name may conflict with a real database.

mysql.dev

Install the MySQL development libraries and header files.

Note

Note that this state is not installed by the mysql meta-state unless you set your pillar data accordingly.

mysql.repo

Add the official MySQL 5.7 repository.

Note

Note that this state currently only supports MySQL 5.7 for RHEL systems. Debian and Suse support to be added. Also need to add the option to allow selection of MySQL version (5.6 and 5.5 repos are added but disabled) and changed enabled repository accordingly.

mysql.config

Manage the MySQL configuration.

Note

There are currently two common ways to configure MySQL, a monolithic configuration file or a configuration directory with configuration files per component. By default this state will use a configuration directory for CentOS and Fedora, and a monolithic configuration file for all other supported OSes.

Whether the configuration directory is used or not depends on whether mysql.config_directory is defined in the pillar. If it is present it will pick the configuration from individual component keys (mysql.server, mysql.galera, mysql.libraries, etc) with optional global configuration from mysql.global. The monolithic configuration, however, is defined separately in mysql.config.