You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allowing configuration of mysql_replication_hostgroups in proxysql.cnf, rather than requiring admin SQL commands to configure them would allow proxysql to more easily be operated in an automated manner, in particular in dockerized environments where containers are expected to start up and be useable completely hands-off.
My current workaround is to build my container with a seed sqlite3 database containing that particular table with the row I need the passing the --reload flag on startup to get proxysql to merge my .cnf based configuration with my desired replication hostgroup configuration.
Thanks for considering.
The text was updated successfully, but these errors were encountered:
Hi Ryan.
I confirm that right now is not possible to configure mysql_replication_hostgroups via config file.
I will get this feature implemented as soon as possible, possibly this week.
Thanks.
Now Admin supports the configuration of mysql_replication_hostgroups from configfile.
That means that also LOAD MYSQL SERVERS FROM CONFIG is responsible for configuring mysql_replication_hostgroups.
This commit also allows comments in config file for `mysql_servers` and `mysql_replication_hostgroups` , related to #643
Allowing configuration of mysql_replication_hostgroups in
proxysql.cnf
, rather than requiring admin SQL commands to configure them would allow proxysql to more easily be operated in an automated manner, in particular in dockerized environments where containers are expected to start up and be useable completely hands-off.My current workaround is to build my container with a seed sqlite3 database containing that particular table with the row I need the passing the
--reload
flag on startup to get proxysql to merge my.cnf
based configuration with my desired replication hostgroup configuration.Thanks for considering.
The text was updated successfully, but these errors were encountered: