The following have not been implemented:

• --defaults-file

The absence of the ability to use a Mysql Config (my.cnf) file for connection config is bad for automation:

• it forces a password to be set in the command line

• it leads to the possibility that the password appears in logs and is shipped off somewhere

• it removes the ability to check if a password should change by detecting a change in the cnf file

Use case: 

As PMM user I need to be able to specify  --defaults-file flag as a path to .cnf file and keep my credentials enrypted so that I can skip passing --user-name and --password  options while adding DB and they will be extracted from config file 

UI:

 Also, Feature should be available by API (for future UI  improvements) and follow common logic - implement logic in pmm-agent, not  pmm-admin 

Note:

• this is username and password related. We are not adding support of other fields from config file

• If password changed  - user need to re-add Service to the system, as it goes with usual --password/–username  flags 

Out of scope:

• Handling non-encrypted credentials.

Suggested solution:

•  If reading plain text defaults (https://jira.percona.com/browse/PMM-4879) fails, try to get the config values using my_print_defaults.

• my_print_defaults should be in PATH

• Program docs: https://dev.mysql.com/doc/refman/5.6/en/my-print-defaults.html

Related PR:

https://github.com/percona/pmm-admin/pull/171