woyten
Joined 3 years ago
Karma
38
Submissions
29
Member since
May 8
Recent submissions
Comment · 8 months ago
Currently working on adding MySQL support to Greenmask (a database anonymization and synthetic data generation tool).
The interesting part is that it’s not just about adding another database driver. I’m revisiting a big part of the codebase and introducing a framework that should make implementing support for new DBMSs much simpler. The goal is to make Greenmask more extensible so that the community can add support for other databases without needing to dig through the entire internal architecture.
Published the first beta of this new approach a few months ago, and now the focus is on stabilizing it and making it production-ready.
MySQL support discussion: https://github.com/GreenmaskIO/greenmask/issues/222
Beta release: https://github.com/GreenmaskIO/greenmask/releases/tag/v1.0.0...
Comment · 1 year ago
In case you don’t have FKs you could specify virtual foreign keys in Greenmask.
Check out docs for details
https://docs.greenmask.io/latest/database_subset/#virtual-re...
Comment · 2 years ago
May I ask how often and in what situations you deal with data import tasks like these? This would help me better understand the issue and make the product more user-friendly. I would appreciate your input.
Comment · 2 years ago
Hi! Thank you for the feedback. I completely understand your concern and agree with you. It can indeed be difficult to get started, and we need to provide clearer use cases with examples to demonstrate the basic concepts and features. I’ll be working on revising the documentation soon to make it easier to follow.
Comment · 2 years ago
> that a schema migration or code deployment would?
> provide GUI and governance controls on top of that?
Exactly. Data doesn’t exist in isolation. Databases are dependencies of services, and schemas evolve throughout the software lifecycle, often managed by different data migration tools. In large organisations, regular developers usually don’t have direct access to the data sources, and masking rules along with real data sources are often restricted. Schema changes must be validated by the responsible data governance teams to ensure compliance and accuracy.
That’s why we implemented the validate command even in this standalone tool, which checks for schema differences and prevents running a dump if any schema changes are detected with detailed warnings. https://docs.greenmask.io/latest/commands/validate
I once presented Greenmask at an event organized by Percona in Cyprus, and one of the questions raised was: “What if we have a staging database, but instead of cleaning up the database and data, we want to add something to the existing dataset?” At the time, I didn’t have an immediate answer. However, this question inspired me to think, and eventually, I found a solution that at least partially covers this case:
You can restore data in topological order by preserving references and ensuring proper dependency handling (https://docs.greenmask.io/latest/commands/restore/#restorati...)
You can exclude non-critical errors to streamline the process without disrupting key operations (https://docs.greenmask.io/latest/configuration/#restoration-...)
I want to emphasize that this type of software must be flexible and adaptable to meet the ever-evolving needs of businesses… Otherwise, the project is as good as dead.
——————————
> And I wonder if it would be worth talking to folks who do SOC 2 auditing
I’ve had discussions with professionals from Information Security, including those working in SOCs, and you're absolutely pointing in the right direction. At the moment, I’m actively exploring solutions and building a concept. I believe that by 2025, we’ll be able to showcase something new.
Comment · 2 years ago
Thank you! I’m really happy that Greenmask meets your expectations
Comment · 2 years ago
Hi! Thank you for your kind words.
> The easier the tool is to use, the harder it might be to monetize... but there are so many applications of a tool like this
I am in favour with you! That’s exactly why we've started developing our Dynamic Staging Environments platform. It will integrate seamlessly with CI/CD systems, enabling to generate, create and maintain stateful components of your services more efficiently.
One key insight we’ve gained is that this type of software introduces new responsibilities across the Dev, Business, and Security teams within a company. This can result in complex processes and interactions. For example, changes to schemas often require approvals from both the security team and service owners, which can slow down workflows. That's why I really appreciate how Bytebase (https://www.bytebase.com/) tackled this issue—by providing a platform that combines GitOps for stateful resources with business logic in a streamlined way. We should be looking in this direction.
Important Remark:
Current design of Greenmask fits well with future plathform. We remain committed to focusing on simple utilities, as they are essential—especially for small businesses. These tools serve a critical purpose by solving problems quickly for smaller companies and for individuals who need a solution that works ASAP.
Comment · 2 years ago
Hi! Noted. Alternatively, you can use the validate command, which will show you the transformation differences:
https://github.com/GreenmaskIO/greenmask