Automate generation of anonymized data set from production

[daveoconnor]

With changes made to how commit authors' names are displayed in reports and in the avatars across the site (e.g. the list of contributors on the releases page), the only way developers can get an accurate representation of how the production site will display commit author's names is by having data that mostly matches the production site.

The reason for this is we're using the github url from the stored commit data to associate commit data with the user account based on the github_username data from the Users table. This github_username data is only set when a user sets it, or connects the account via SSO where it is inserted automatically.

It would be useful to have an automated process that dumps the production data and anonymizes sensitive data (e.g. any passwords) that we as devs could download, maybe from a generated link placed into passbolt?

[rbbeeston]

@sdarwin I'm sending this to you but feel free to re-assign if someone else should do it.

[sdarwin]

@daveoconnor do you agree Django does not store passwords in the database as clear text.

Try this and let me know your opinion of the strategy.

• Install gcloud cli locally. https://cloud.google.com/sdk/docs/install .
• Auth to gcloud, based on the email address that was previously configured to view google's Cloud Logging.

gcloud storage ls --project=boostorg-project1 gs://boostbackups/db1/daily/boost_production*
gcloud storage cp --project=boostorg-project1 gs://boostbackups/db1/daily/boost_production.db1-2.2025-02-25-08-00-01.dump .