Skip to content

How to get PYNONYMIZER_MYSQL_CMD_OPTS to work with socket ? #172

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

Open
flybyray opened this issue Aug 9, 2024 · 0 comments
Open

How to get PYNONYMIZER_MYSQL_CMD_OPTS to work with socket ? #172

flybyray opened this issue Aug 9, 2024 · 0 comments

Comments

@flybyray
Copy link

flybyray commented Aug 9, 2024

Describe the bug

With version 1.25 the following command worked

pynonymizer  \
--db-type mysql  \
--db-host localhost  \
--db-user root  \
--db-name open_data  \
--strategy /var/lib/mysql_instances/open-data-33019/anonymize/20.0.0/open-data-strategy.yml  \
--mysql-cmd-opts="--socket=/some/path/to/var/run/mysqld/mysqld.sock" \
--only-step ANONYMIZE_DB

with 2.4.0 this is not possible anymore.

How to connect to mysql socket?

Expected behavior
mysql cmd opts should be first handled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant