From f6b334bc092ea97e95491b58b9d42bae7e7f05cc Mon Sep 17 00:00:00 2001 From: Deivids Briedis Date: Fri, 15 Mar 2024 13:24:45 +0200 Subject: [PATCH] gdprDump user preservation --- README.md | 4 ++++ silta/silta-main.yml | 6 ++++++ 2 files changed, 10 insertions(+) diff --git a/README.md b/README.md index 120cf1c0..49d63710 100644 --- a/README.md +++ b/README.md @@ -116,3 +116,7 @@ To use these commands, you need a secret key that is used to encrypt and decrypt You should use the following naming convention for your custom keys: `SEC_{PROJECT_NAME}_{CONTEXT}` where `CONTEXT` refers to the environment you are working on, such as `silta_dev` (development context) or `silta_finland` (production context). For example, if you are working on the `drupal-project` project in the `silta_dev` environment, you should use the `SEC_DRUPAL_PROJECT_SILTA_DEV` key. The `silta/silta.secret` file is a YAML file that contains the encrypted secrets for your project in the default `silta-dev` context. You can add more files for other contexts, such as `silta/silta-prod.secret` for the production context. + +### GDPR requirements +User data in feature environments is sanitized using [Smile-SA/gdpr-dump tool](https://github.com/Smile-SA/gdpr-dump). In order to preserve certain users, +you can uncomment the gdprDump code block in silta-main.yml and specificy user IDs which need to be preserved. \ No newline at end of file diff --git a/silta/silta-main.yml b/silta/silta-main.yml index 73583dc8..4a05be11 100644 --- a/silta/silta-main.yml +++ b/silta/silta-main.yml @@ -5,3 +5,9 @@ php: drupal: # In main environment, run cron once an hour. Adjust as needed. schedule: '~ * * * *' + +# Prevent specific users from being sanitizied on feature environments. +# gdprDump: +# tables: +# users_field_data: +# skip_conversion_if: 'in_array({{uid}}, [1, 2, 3])' \ No newline at end of file