Pynonymizer

Latest version: v2.3.1

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

Scan your dependencies

Page 7 of 8

1.5.0

Added
- Added Support for different strategyfile formats: `.json`/`.yaml`/`.yml`
- Added option `--seed-rows`: specify the seed row size for fake data generated.
- Added MSSQL provider: use `--db-type/-t mssql`
- Added MSSQL option `---mssql-backup-compression` and added convention for provider-specific arguments (prefixed by `dbtype-`)
- Added optional table strategy key: `schema`. For supported databases (mssql), you can now specify the schema of the table strategy.
- Added strategy parsing mode for multi-table and multi-column updates of the same table/column names
Changed
- Changed mandatory arguments for main process to account for different process step permutations:
- input is optional if `RESTORE_DB` is skipped
- strategyfile is optional if `ANONYMIZE_DB` is skipped
- output is optional if `DUMP_DB` is skipped
- db_name is mandatory if a step prevents it from being determined automatically e.g. strategyfile is missing

1.4.1

Fixed
- Fixed an issue where import syntax was preventing certain modules from being loaded in python 3.6

1.4.0

Added
- Added **all** faker providers to the `fake_update` type.
- Added `fake_args` kwargs key to the `fake_update` type. You can now make use of parameterized providers in faker!
- Added "verbose-style" strategy format to complement original shorthand autodetection.
- Added `where` option for where-clause support on all update_column strategies. Columns with a matching where option are grouped together for execution.
- Added Stock strategies for sylius and wordpress 4.4 in the main repository.
- Added column strategy: `literal` for setting literal values e.g. `RAND()`, `'A String'`
Changed
- Changed parsing for mapping column strategy keys to classes: Parser no longer ignored unused keys

1.3.0

Added
- Added `scripts` strategyfile section. you can now specify `before` and `after` scripts to be run decorating the anonymization process. (see doc/strategyfiles.md)
- Added Process steps, e.g. `CREATE_DB`, `ANONYMIZE_DB` for improved logging and skip behaviour (see doc/process-control.md)
- Added process control options:
- `--start-at STEP`: choose a step to start at (inclusive)
- `--stop-at STEP`: choose a step to stop at (inclusive)
- `--skip-steps STEP [..STEP]` : specify one or more steps to skip in the process
Changed
- Changed the way mysql provider handles execution so CalledProcessErrors no longer expose all command parameters by default.
Fixed
- Fixed some minor spelling errors in the help text.
- Fixed an issue where dumping an empty database(unlikely, but still possible) could cause an unhandled exception.

1.2.0

Added
- Added new environment variables, optionals for all arguments. See the help `pynonymizer -h` for more information
Changed
- Changed Internal structure to assist with better testing.
Deprecated
- Deprecated positional arguments. These will no longer appear in helptext and are not required. You can now use all-environmental, all-optional or a mix of both.
Going forward, The preferred solution is `--optional-vars` or environment variables.
- Deprecated old environment variables in favour of new prefix `PYNONIMIZER_`.
These will continue to work but will be removed in a future release.
- `DB_TYPE -> PYNONYMIZER_DB_TYPE`
- `DB_HOST -> PYNONYMIZER_DB_HOST`
- `DB_NAME -> PYNONYMIZER_DB_NAME`
- `DB_USER -> PYNONYMIZER_DB_USER`
- `DB_PASS -> PYNONYMIZER_DB_PASSWORD`
- `FAKE_LOCALE -> PYNONYMIZER_FAKE_LOCALE`

1.1.2

Added
- Added `-v` `--version` flag argument. [4]
- Added additional metadata to `setup.py` for better PyPI info. [3]

Page 7 of 8

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.