Config files are loaded in an order that hinders automation
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.5 |
Confirmed
|
Undecided
|
Unassigned | |||
5.6 |
Confirmed
|
Undecided
|
Unassigned | |||
5.7 |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
On a fresh install of percona-
├── conf.d
│ ├── mysql.cnf
│ └── mysqldump.cnf
├── my.cnf
├── my.cnf.fallback
├── my.cnf.old
├── percona-server.cnf
└── percona-
├── mysqld.cnf
└── mysqld_safe.cnf
When using ansible for provisioning, it's useful to be able to drop in a file with settings that can override the defaults. However, due to the order in which the files are included in my.cnf:
!includedir /etc/mysql/conf.d/
!includedir /etc/mysql/
it would seem the only way to do this would be to add a file in /etc/mysql/
A simpler solution might be to reverse the order of the includes like this:
!includedir /etc/mysql/
!includedir /etc/mysql/conf.d/
in order that the standard Percona settings are loaded first, and any file dropped into the /etc/mysql/conf.d/ directory can override these settings.
tags: | added: pkg |
Thank you for the report.
I assume you are using ansible for provisioning not only Percona Servers, but also upstream MySQL Servers? In this case this request makes sense. But at the other time it may break existing installations where users relied on current behavior.
I will mark this report "Confirmed", but do not get it as promise it will be eventually fixed. We should care about backward incompatibility very seriously. I personally would vote against fixing this.