{"id":115290,"date":"2024-04-24T15:22:34","date_gmt":"2024-04-24T13:22:34","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/reliz-instrumenta-dlya-anonimizaczii-baz-dannyh-nxs-data-anonymizer-1-4-0"},"modified":"2024-04-24T15:22:34","modified_gmt":"2024-04-24T13:22:34","slug":"reliz-instrumenta-dlya-anonimizaczii-baz-dannyh-nxs-data-anonymizer-1-4-0","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/reliz-instrumenta-dlya-anonimizaczii-baz-dannyh-nxs-data-anonymizer-1-4-0","title":{"rendered":"Release of the nxs-data-anonymizer tool for database anonymization 1.4.0","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
nxs-data-anonymizer 1.4.0 has been released \u2014 a tool for anonymizing database dumps for PostgreSQL and MySQL\/MariaDB\/Percona. The utility supports data anonymization based on templates and functions from the Sprig library. Among other things, it can use values from other columns for the same row to populate the anonymized data. The tool can be used via unnamed pipes in the command line, allowing a dump from the source database to be redirected directly into the target database with the necessary transformations. The tool is written in Go and is released under the Apache License 2.0. <\/p>\n
Less than a year after the first release of version 1.0.0, the tool has gained the following features: <\/p>\n
\n
A filter function has been added to work with null values.\n
The -l\/\u2014log-format command has been implemented, allowing the selection of the logging format (json or plain).\n
Progress indication for the anonymization process has been added \u2014 progress information is displayed at specified intervals during the operation.\n
Version 1.4 introduced the ability to set field values using external commands by adding 'type: command' to the column value. For example: filters: some_table_name: columns: some_column_name: type: command value: \/path\/to\/command\/or\/script.sh\n
If 'type: command' is specified for a column, the value field is treated as a file path to the command that will be executed each time for that field. During the execution of the command, additional environment variables will be available: <\/p>\n
\n
ENVVARTABLE={TABLE_NAME}: contains the name of the filtered table\n
ENVVARCOLUMN_{COLUMN_NAME}={COLUMN_VALUE}: contains all columns and their values (before replacement) for the current filtered row. The stdout of the command is considered as the new value for the filtered field. <\/ul>\n<\/ul>\n