Pynonymizer

Latest version: v2.2.1

Safety actively analyzes 627310 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 7

1.21.0

Added
- Added Custom Providers to strategyfiles. You can now include custom Faker providers in your
strategyfiles, using the `providers` top-level key.
- Added Locale key `locale`(top-level) to strategyfiles. This is designed to replace the `-l`/`--fake-locale` CLI option.
Deprecated
- Deprecated `-l`/`--fake-locale` option. You should use the `locale` key in your strategyfile.
This will be removed in a future release.
Fixed
- Fixed a bug in postgres where table and column names were not consistently escaped.
- Fixed some documentation errors.

1.20.0

Fixed
- Fixed a bug where postgres tables could not be anonymized if they contained a json or jsonb column.

1.19.0

Added
- Added a new compact syntax for column strategy `literal`. Surrounding your value in parentheses `()` will select the literal strategy.
- Added new cli option `--only-step` to select a step to run. Useful for running anonymization routines without having to use start-at and stop-at simultaneously. e.g. `--only-step ANONYMIZE_DB`.

Changed
- Improvements to mssql driver auto-selection process, to attempt to select a more recent driver by default.
Fixed
- Fixed a bug where on a system with no ODBC drivers, an incorrect error would be thrown.

1.18.1

Fixed
- Fixed a fatal error when deprecated environment vars were used (See 1.2.0 notes for a full list).

1.18.0

Added
- Added Integration tests for MSSQL
- Added Driver auto-selection for MSSQL. This should find the correct driver on different systems. Where multiple drivers are detected a warning will be issued, and the first driver will be selected. To override this behaviour, you can specify the driver manually using cli opt `--mssql-driver / $PYNONYMIZER_MSSQL_DRIVER`
- Added support for remote servers in MSSQL, provided RESTORE_DB/DUMP_DB is not being used.
- Added support for MSSQL servers using custom ports.
Changed
- Changed Integration tests to show cmd output better in CI.
- Changed MSSQL connection behaviour: provider will now allow truncation using `ANSI_WARNINGS off;` when updating tables.
- Changed verbose-mode behaviour to include more information via debug logs during CLI runs.
Fixed
- Fixed an issue in MSSQL where anonymization would be deterministically applied to all rows the same instead of distributed.
- Fixed a typo in mssql, mysql and postgres when running strategy before/after scripts.

1.17.0

Added
- Added New _additional-opts_ style parameters which allow you to control the behaviour of the underlying dump and restore tools more effectively.
`*-cmd-opts` will be appended to the batched restore subprocess, while `*-dump-opts` will be appended to the dump (pgdump, mysqldump) subprocess
These are advanced features and can seriously modify or even break the behaviour of pynonymizer. Use with caution!
* `--mysql-cmd-opts/$PYNONYMIZER_MYSQL_CMD_OPTS`
* `--postgres-cmd-opts/$PYNONYMIZER_POSTGRES_CMD_OPTS`
* `--postgres-dump-opts/$PYNONYMIZER_POSTGRES_DUMP_OPTS`
- Added cli warnings for deprecated positional arguments and environmental variables.
- Added Python 3.9 to official support description(pypi) and unit test targets.
Changed
- Changed order of `additional_args` for Mysql dump runner, so additional options are added _after_ the existing args.
Fixed
- Fixed a bug where `$PYNONYMIZER_VERBOSE` was not being detected correctly.

Page 3 of 7

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.