[16.0][IMP] core: Introducing a new CLI command for database anonymization. #116739
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
C3POdoo
requested review from
a team,
xmo-odoo and
ryv-odoo
and removed request for
a team
Just like with database neutralization we sometimes have a need to additionally anonymize some very sensitive module data from leaving production environment, but that can be conditioned depending on the target environment because, for example, we want to have one staging environment neutralized, but the other or all integration envs we want them neutralized and anonymized as well.
pnajman-modoolar
force-pushed
the
imp/16.0/core/cli-anonymize
branch
from
88f9334
to
27e9202
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi guys,
I have a proposition for a new
clicommand. I hope you'll like the idea ...Just like with database neutralization we sometimes have a need to additionally anonymize some very sensitive module data from leaving production environment, but that can be conditioned depending on the target environment because, for example, we want to have one staging environment neutralized, but the other or all integration envs we want them neutralized and anonymized as well.
Cheers,
Petar
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr