Skip to content

Releases: GreenmaskIO/greenmask

v0.1.13

07 May 07:19
ef3e2e9
Compare
Choose a tag to compare

Greenmask 0.1.13

This release introduces only improvements in documentation deployment. The core greenmask utility does not contain any changes.

Changes

  • Added documentation deployment with versioning

Contributors

@tarbaev-vl

v0.1.12

29 Apr 20:05
611a8ae
Compare
Choose a tag to compare

Greenmask 0.1.12

This release introduces improvements and bug fixes

Changes

  • Fixed config decoding issue
  • Fixed TOC entries merge behavior when the data section is empty
  • Fixed integration tests for S3 storage

Contributors

@wwoytenko

Special thanks

@viniciuschiele

v0.1.11

28 Apr 08:11
e2d52dd
Compare
Choose a tag to compare

Greenmask 0.1.11

This release introduces improvements and bug fixes

Changes

  • Added support for generated columns in the table #77
  • Fixed transformer parameters encoding issue caused by spf13/viper #76
  • Fixed table scoring for transformed table
  • Refactored connection management logic in restore command - fixes connection idle timeout #75

Contributors

@wwoytenko
@tarbaev-vl

Special thanks

@janmeier
@dani
@MamesPalmero

v0.1.10

17 Apr 16:09
48c5fd0
Compare
Choose a tag to compare

Greenmask 0.1.10

This release introduces improvements and bug fixes

Changes

  • Fixed panic caused in RandomString transformer
  • Fixed wrong table size calculation. Now the table size includes TOAST table size
  • Added custom transformer interaction API defaults if not set
  • Changed docker workdir to greenmask home
  • Removed bucket name from object path prefix

Contributors

@joao-zanutto
@wwoytenko

Special thanks

@janmeier
@dani

v0.1.9

06 Apr 09:02
c5e6324
Compare
Choose a tag to compare

Greenmask 0.1.9

This release introduces improvements and bug fixes

Improvements

  • Implemented tables scoring according to the table size and transformation costs. This correctly spreads the tables dumping
    between the requested worker's pool and reduces the execution time. Now greenmask introspects the table size, adds
    the transformation scoring using the formula
    score = tableSizeInBytes + (tableSizeInBytes * 0.03 * tableTransformationsCount), and uses the strategy "Largest
    First". The problem is described here
  • Introduced no_verify_ssl parameter for S3 storage
  • Adjusted Dockerfile
    • Changed entrypoint to greenmask binary
    • The greenmask container now runs under greenmask user and groups
  • Refactored storage config structure. Now it contains the type that is used for the storage type determination
  • Most of the attributes may be overridden with environment variables where the letters are capitalized and the dots
    are replaced with underscores. For instance, the setting storage.type might be represented with the environment
    variable STORAGE_TYPE
  • Parameter --config is not required anymore. This simplifies the greenmask utility user experience
  • Directory storage set as the default
  • Set the default temporary directory as /tmp
  • Added environment variable section to the configuration docs

Fixes

  • Fixed S3_REGION environment variable usage. Tested cases where the S3 storage is set up using S3 variables that
    uses by github.com/aws/aws-sdk-go
  • Updated project dependencies to the latest version

Contributors

@joao-zanutto
@wwoytenko

Special thanks

@janmeier

v0.1.8

25 Mar 13:02
f0242a9
Compare
Choose a tag to compare

Greenmask 0.1.8

This release introduces improvements and bug fixes

Improvements

  • Implemented --exit-on-error parameter for pg_restore run. But it does not play for "data" section restoration now. If any error is caused in data section greenmask exits with the error whether --exit-on-error was provided or not. This might be fixed later

Fixes

  • Fixed dependent objects dropping when running with the restore command with the --clean parameter. Useful when restoring and overriding only required tables
  • Fixed show-dump command output in text mode
  • Disabled CGO. Fixes problem when downloaded binary from repo cannot run
  • Fixed delete dump operation

Contributors

@wwoytenko

v0.1.7

15 Mar 21:16
4cf2864
Compare
Choose a tag to compare

Greenmask 0.1.7

This release introduces improvements, bug fixes, and documentation updates.

New features

  • Added restoration filtering by --table, --schema and --exclude-schema parameters
  • Validate command without parameters validates only the configuration file
  • Added the --schema parameter, which allows to make a schema diff between the previous dump and the current. This
    is useful when you want to check if the schema has changed after the migration. By controlling it we can exclude
    data leakage after migration
  • Validate command divided by many stages that can be controlled using parameters
    • Configuration validation
    • Transformer validation
    • Constraint violation check
    • Data difference check
    • Schema difference check

Improvements

  • Improved Hash transformer
    • Added salt parameter that can be set via config or via GREENMASK_GLOBAL_SALT
    • Added sha3 functions support in different modes (sha3-224, sha3-256, sha3-384, sha3-512)
  • Refactored Cmd transformer logic
    • Json API: Now it allows to use of column names instead of column indexes in JSON format
    • Csv API: Now it can use the column order from config via column remapping
  • The validate command was rewritten almost from scratch.
    • New option --transformed-only - displays only columns that are transformed with a primary key (if exists). This
      allows to reduce the output data and make it more readable
    • Implemented json format for output
    • Added the --table-format parameter which is responsible for the vertical and horizontal table orientation.
      This works only when --format=text
    • Added the --warnings parameter, if it is specified then not only fatal-warnings will be displayed, but also
      those with a lower severity

Fixes

  • Fixed --use-list option - now it applies to entries according to the order in the list file
  • Fixed --use-list option behavior together with --list-format option (json or text). Now it
    generates a temporal list file in text format for providing it to the pg_restore call
  • Updated documentation according to the latest changes

Contributors

@wwoytenko

v0.1.6

23 Feb 11:05
7f7f6a6
Compare
Choose a tag to compare

Greenmask 0.1.6

This is a minor release that introduces a bug hotfix

Fixes

  • Fixed uncontrolled buffer growth in the restore command #22

Contributors

@wwoytenko

Special thanks

@janmeier

v0.1.5

16 Feb 19:59
c0977a1
Compare
Choose a tag to compare

Greenmask 0.1.5

This release introduces a new Greenmask command, improvements, bug fixes, and numerous documentation updates.

New features

Added a new Greenmask CLI command — show-transformer that shows detailed information about a specified transformer.

Improvements

  • The Hash transformer has been completely remastered and now has the function parameter to choose from several hash algorithm options and the max_length parameter to truncate the hash tail.
  • Split information about transformers between the list-transformers and new show-transformer CLI commands, which allows for more comprehensible and useful outputs for both commands
  • Added error severity for the Cmd parameter validator
  • Improved UX for the Greenmask release binaries
  • Moved documentation from greenmask-docs
  • Significantly refactored the structure and content of documentation

Fixes

  • Fixed metadata enrichment for validation warnings caused by RawValueValidator
  • Fixed a typo in the credit_card value for the type parameter of the Masking transformer
  • Fixed Greenmask Playground environment variables and the cleanup command
  • Fixed list-dump, list-transformers, and restore commands exit code on error

Contributors

@tarbaev-vl
@gracingpro
@ginstagram
@wwoytenko

Special thanks

@viniciuschiele

v0.1.4

07 Feb 19:39
9e4afa1
Compare
Choose a tag to compare

Greenmask v0.1.4 - PostgreSQL Dump and Obfuscation Tool

This release introduces bug fixes.

Fixes:

  • Fixed database connection string behavior fields #6

Special thanks:

@viniciuschiele