check_private_data.py is a script which reports if there is any database/table/column that is not being filtered correctly.
We spoke sometime ago to schedule the script to be run from time to time and report back if there is any data present that shouldn't be there
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Reporting tests with the private data script | operations/puppet | production | +48 -0 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | jcrespo | T140788 Labs databases rearchitecture (tracking) | |||
| Resolved | jcrespo | T153058 LabsDB infrastructure pending work | |||
| Resolved | Marostegui | T153680 Create a cronjob/check to run check_private_data data script and report back |
Change 328352 had a related patch set uploaded (by Marostegui):
[WIP] Reporting tests with the private data script
I would like to get this deployed by Monday so we can watch its behaviour during the week - worst case scenario it will just spam myself :)
I have pushed that change and I have run puppet on labsdb1009 and the change is looking good.
We will see how it works and how many emails I get per night (hopefully none) :-)
Once we are sure it works fine and consistently fine we can see further steps.
Going to close this for now as the script is working fine as a first measure. Further steps can be discussed later.