base on PostgreSQL database anonymization and synthetic data generation tool # [Greenmask](https://greenmask.io) ## Dump anonymization and synthetic data generation tool **Greenmask** is a powerful open-source utility that is designed for logical database backup dumping, anonymization, synthetic data generation and restoration. It has ported PostgreSQL libraries, making it reliable. It is stateless and does not require any changes to your database schema. It is designed to be highly customizable and backward-compatible with existing PostgreSQL utilities, fast and reliable. [](https://discord.com/invite/rKBKvDECfd) [](https://t.me/greenmask_community) [](https://twitter.com/GreenmaskIO) [](https://github.com/GreenmaskIO/greenmask/actions/workflows/release.yml) [](https://docs.greenmask.io) [](https://github.com/greenmaskio/greenmask/blob/main/LICENSE) [](https://github.com/greenmaskio/greenmask/releases/latest) [](https://somsubhra.github.io/github-release-stats/?username=greenmaskio&repository=greenmask&page=1&per_page=5) [](https://hub.docker.com/r/greenmask/greenmask) [](https://goreportcard.com/report/github.com/greenmaskio/greenmask) [](https://sonarcloud.io/summary/new_code?id=GreenmaskIO_greenmask)  ## Getting started Greenmask has a [Playground](https://docs.greenmask.io/latest/playground/) - it is a sandbox environment in Docker with sample databases included to help you try Greenmask without any additional actions 1. Clone the `greenmask` repository and navigate to its directory by running the following commands: ```shell git clone [email protected]:GreenmaskIO/greenmask.git && cd greenmask ``` 2. Once you have cloned the repository, start the environment by running Docker Compose: ```shell docker-compose run greenmask ``` ## Features * **[Deterministic transformers](https://docs.greenmask.io/latest/built_in_transformers/transformation_engines/#hash-engine)** — Uses hash functions to ensure consistent output for the same input. Most transformers support both `random` and `hash` engines, offering flexibility for various use cases. * **[Dynamic parameters](https://docs.greenmask.io/latest/built_in_transformers/dynamic_parameters/)** — most transformers support dynamic parameters, allowing them to adapt based on table column values. This feature helps manage dependencies between columns and meet constraints effectively. * **[Transformation Condition](https://docs.greenmask.io/latest/built_in_transformers/transformation_condition/)** — applies the transformation only when a specified condition is met, making it useful for targeting specific rows. * **[Transformation validation and easy maintenance](https://docs.greenmask.io/latest/commands/validate/)** — Greenmask provides validation warnings, data transformation diffs, and schema diffs during configuration, enabling effective monitoring and maintenance of transformations. The schema diff feature helps prevent data leakage when the schema changes. * **[Transformation inheritance](https://docs.greenmask.io/latest/built_in_transformers/transformation_inheritance/)** — transformation inheritance for partitioned tables and tables with foreign keys. Define once and apply to all. * **Stateless** — Greenmask operates as a logical dump and does not impact your existing database schema. * **Cross-platform** — Can be easily built and executed on any platform, thanks to its Go-based architecture, which eliminates platform dependencies. * **Database type safe** — Ensures data integrity by validating data and using the database driver for encoding and decoding operations, preserving accurate data formats. * **Backward compatible** — Fully supports the same features and protocols as standard PostgreSQL utilities. Dumps created by Greenmask can be seamlessly restored using the `pg_restore` utility. * **Extensible** — Users have the flexibility to [implement domain-based transformations](https://docs.greenmask.io/latest/built_in_transformers/standard_transformers/cmd/) in any programming language or use [predefined templates](https://docs.greenmask.io/latest/built_in_transformers/advanced_transformers/). * **Parallel execution** — Enables parallel dumping and restoration to significantly speed up results. * **Variety of storages** — Supports both local and remote storage, including directories and S3-compatible solutions. * **[Pgzip support for faster compression](https://docs.greenmask.io/latest/commands/dump/?h=pgzip#pgzip-compression)** — Speeds up dump and restoration processes with parallel compression by setting `--pgzip`. ## Use Cases Greenmask is ideal for various scenarios, including: * **Backup and Restoration**. Use Greenmask for your daily routines involving logical backup dumping and restoration. It seamlessly handles tasks like table restoration after truncation. Its functionality closely mirrors that of pg_dump and pg_restore, making it a straightforward replacement. * **Anonymization, Transformation, and Data Masking**. Employ Greenmask for anonymizing, transforming, and masking backups, especially when setting up a staging environment or for analytical purposes. It simplifies the deployment of a pre-production environment with consistently anonymized data, facilitating faster time-to-market in the development lifecycle. ### General Information The best approach for logical backup dumping and restoration is to use core PostgreSQL utilities, specifically pg_dump and pg_restore. Greenmask is designed to align with these native tools, ensuring full compatibility. It independently manages data dumping while delegating schema dumping and restoration to `pg_dump` and `pg_restore`, ensuring smooth integration with PostgreSQL’s standard workflow. Greenmask utilizes the directory format of `pg_dump` and `pg_restore`, ideal for parallel execution and partial restoration. This format includes metadata files to guide backup and restoration steps. #### Storage Options * **[s3](https://docs.greenmask.io/latest/configuration/#__tabbed_1_2)** - Supports any S3-compatible storage system, including AWS S3, offering flexibility across different cloud storage solutions. * **[directory](https://docs.greenmask.io/latest/configuration/#__tabbed_1_1)** - This is the default option, representing a standard filesystem directory for local storage. #### Data Anonymization and Validation Greenmask works with **COPY lines**, collects schema metadata using the Golang driver, and employs this driver in the encoding and decoding process. The **validate command** offers a way to assess the impact on both schema (**validation warnings**) and data (**transformation and displaying differences**). This command allows you to validate the schema and data transformations, ensuring the desired outcomes during the Anonymization process. #### Customization If your table schema relies on functional dependencies between columns, you can address this challenge using the [Dynamic parameters](https://docs.greenmask.io/latest/built_in_transformers/dynamic_parameters/). By setting dynamic parameters, you can resolve such as created_at and updated_at cases, where the updated_at must be greater or equal than the created_at. If you need to implement custom logic imperatively use [Cmd](https://docs.greenmask.io/latest/built_in_transformers/standard_transformers/cmd/) or [TemplateRecord](https://docs.greenmask.io/latest/built_in_transformers/advanced_transformers/template_record/) or [Template](https://docs.greenmask.io/latest/built_in_transformers/advanced_transformers/template/) transformers. #### PostgreSQL Version Compatibility **Greenmask** is compatible with PostgreSQL versions **11 and higher**. ## Links * [Documentation](https://docs.greenmask.io) * Email: **[email protected]** * [Twitter](https://twitter.com/GreenmaskIO) * [Telegram](https://t.me/greenmask_community) * [Discord](https://discord.com/invite/rKBKvDECfd) * [DockerHub](https://hub.docker.com/r/greenmask/greenmask) ## References * Utilized the [Demo database](https://postgrespro.com/community/demodb), provided by PostgresPro, for integration testing purposes. * Employed the [adventureworks database](https://github.com/morenoh149/postgresDBSamples) created by `morenoh149/postgresDBSamples`, in the Docker Compose playground. ", Assign "at most 3 tags" to the expected json: {"id":"11998","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"