-
Notifications
You must be signed in to change notification settings - Fork 656
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Config file revamp #581
Comments
Any timeline on this? Seeing as mycli just fails completely if it is not allowed to create |
Removing support for my.cnf does not make sense to me, for a MySQL tool. I find it very useful to use the same configuration file with both mycli and the mysql command line client in scripts. This is also a nice selling point to new users who are mostly familiar with the standard client. |
@greenskeleton removing my.cnf was never a deliberate decision, it stopped working because of a bug. We just released version 1.24.1 to pypi that should have this functionality restored. |
@pasenor I did happen to catch the commit in master that fixed my.cnf prior to the release today, thanks! I was referring to the task from first issue comment:
|
I agree with this. Please don't remove support for the .my.cnf file. I have many .my-project.cnf files with the correct defaults for my different projects, and I symlink .my.cnf to .my-project.cnf to use Edit: I came here looking for a way to set a default database for mycli in the .my.cnf file. The problem is mycli only reads the IMO, reading the .my.cnf file is a great feature, to make transitioning from the default mysql client easy and to support using multiple tools ( Edit2: an easy workaround to read the database from the .my.cnf file
|
In mycli, managing the config has been challenging for awhile since we have five places a user can configure their experience, three of which are config files.
~/.my.cnf
file ([client]
section)~/.mylogin.cnf
~/.myclirc
This issue documents the overall revamp of the config that we're trying to accomplish for version 2.
Tasks
.my.cnf
and.mylogin.cnf
to the mycli config file (allows user input to override this feature and control password migration).my.cnf
and.mylogin.cnf
-- "one config file to rule them all"Missing options in mycli's config file to consider adding
These options are currently supported in mycli via the
.my.cnf
file, so we need to consider adding them to mycli's config file.Assorted Background Notes
Previous config-related discussions:
The desire is to balance these three things well:
There has been extensive discussion about the false sense of security that the encrypted login path file provides users. Many users have noted how it's not a security feature. In fact, if you have a copy of someone's login path file, you can decrypt it with a single command:
python -c 'from mycli.config import *;print(read_config_file(open_mylogin_cnf(get_mylogin_cnf_path())))'
Mycli now supports storing host/port/database information in its config file: http://www.mycli.net/loginpath#dsn
Another long-term goal is keyring support so that users can use their system's password manager with mycli.
The text was updated successfully, but these errors were encountered: