Merge db-tools:gdprify and db-tools:anonymize for a more GDPR-friendly workflow
#75
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
Lonnytunes
reviewed
Dec 14, 2023
Lonnytunes
reviewed
Dec 14, 2023
Lonnytunes
reviewed
Dec 14, 2023
SimonMellerin
commented
Dec 14, 2023
apply suggestions Co-authored-by: Lonnytunes <[email protected]>
SimonMellerin
changed the title
db-tools:gdprify and db-tools:anonymize for a more GDPR-friendly workflow
auto-merge was automatically disabled
December 19, 2023 08:15
Pull request was converted to draft
pounard
requested changes
Dec 19, 2023
pounard
approved these changes
Dec 19, 2023
Lonnytunes
reviewed
Dec 19, 2023
Lonnytunes
reviewed
Dec 19, 2023
Lonnytunes
reviewed
Dec 19, 2023
Lonnytunes
reviewed
Dec 19, 2023
Lonnytunes
reviewed
Dec 20, 2023
Lonnytunes
reviewed
Dec 20, 2023
Lonnytunes
reviewed
Dec 20, 2023
Lonnytunes
reviewed
Dec 20, 2023
Lonnytunes
reviewed
Dec 20, 2023
Lonnytunes
reviewed
Dec 20, 2023
Lonnytunes
reviewed
Dec 20, 2023
Co-authored-by: Lonnytunes <[email protected]>
Lonnytunes
reviewed
Dec 20, 2023
Co-authored-by: Lonnytunes <[email protected]>
Lonnytunes
reviewed
Dec 20, 2023
Lonnytunes
reviewed
Dec 20, 2023
Lonnytunes
reviewed
Dec 20, 2023
Lonnytunes
reviewed
Dec 20, 2023
Co-authored-by: Lonnytunes <[email protected]>
Lonnytunes
reviewed
Dec 20, 2023
Lonnytunes
reviewed
Dec 20, 2023
|
|
||
| ## Options | ||
|
|
||
| You can specify the behaviour of the `db-tools:anonymize`command with some options detailed below. |
There was a problem hiding this comment.
Suggested change
| You can specify the behaviour of the `db-tools:anonymize`command with some options detailed below. | |
| You can modify the behaviour of the `db-tools:anonymize` command with some options detailed below. |
Lonnytunes
reviewed
Dec 20, 2023
Lonnytunes
reviewed
Dec 20, 2023
| ### Do not restore initial state after anonymization | ||
|
|
||
| You can choose to not restore initial database with the `--no-restore` option. | ||
| With this option, step 1 and 5 will be skipped during execution. |
There was a problem hiding this comment.
Suggested change
| With this option, step 1 and 5 will be skipped during execution. | |
| With this option, steps 1 and 5 will be skipped during execution. |
Lonnytunes
reviewed
Dec 20, 2023
Lonnytunes
reviewed
Dec 20, 2023
| ### Split update queries | ||
|
|
||
| By default, the anonymization process use one update query per table. | ||
| For debug purpose, it could be usefull to run not only one update query per table |
There was a problem hiding this comment.
Suggested change
| For debug purpose, it could be usefull to run not only one update query per table | |
| For debug purpose, it could be useful to run not only one update query per table |
Lonnytunes
reviewed
Dec 20, 2023
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.
No description provided.