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
Current Behavior
The mysqld_exporter supports environment variable for configuration, including MYSQLD_EXPORTER_PASSWORD for specifying the MySQL password. However, when using Docker Swarm secrets, there's no support for the _FILE suffix pattern that is commonly used for secure password handling.
Expected Behavior
The exporter should support reading the MySQL password from a file using MYSQLD_EXPORTER_PASSWORD_FILE, similar to how other Docker-oriented applications handle secrets. This would allow secure integration with Docker Swarm secrets.
Use Case
When deploying mysqld_exporter in a Docker Swarm environment, we want to use Docker secrets for managing sensitive credentials. The current implementation requires passing the password directly as an environment variable, which is less secure than using Docker secrets.
Current Behavior
The mysqld_exporter supports environment variable for configuration, including
MYSQLD_EXPORTER_PASSWORD
for specifying the MySQL password. However, when using Docker Swarm secrets, there's no support for the_FILE
suffix pattern that is commonly used for secure password handling.Expected Behavior
The exporter should support reading the MySQL password from a file using
MYSQLD_EXPORTER_PASSWORD_FILE
, similar to how other Docker-oriented applications handle secrets. This would allow secure integration with Docker Swarm secrets.Use Case
When deploying mysqld_exporter in a Docker Swarm environment, we want to use Docker secrets for managing sensitive credentials. The current implementation requires passing the password directly as an environment variable, which is less secure than using Docker secrets.
Example desired usage:
The text was updated successfully, but these errors were encountered: