Skip to content

Commit e49743d

Browse files
committed
Updating name of script in DEVELOPERS.md
1 parent d4ff019 commit e49743d

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

DEVELOPERS.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -133,8 +133,8 @@ GRANT ALL PRIVILEGES on database jobserver to jobsuser;
133133

134134
Copies of production can be restored to a local database using a sanitised dump pulled from production.
135135

136-
##### dump_db script
137-
The sanitised dump is created using `dump_db` job that runs daily. The job builds a temporary schema (`temp_scrubbed_schema`) that contains a copy of each table but with only allowlisted columns populated fetched from `allow_list.json`. All other columns are replaced with type-appropriate fake values. Once the schema is populated, the job drops this temporary schema.
136+
##### dump_sanitised_db.py
137+
The sanitised dump is created using `dump_sanitised_db` job that runs daily. The job builds a temporary schema (`temp_scrubbed_schema`) that contains a copy of each table but with only allowlisted columns populated fetched from `allow_list.json`. All other columns are replaced with type-appropriate fake values. Once the schema is populated, the job drops this temporary schema.
138138

139139
##### allow_list.json
140140
The scrubbed dump is driven by `jobserver/jobs/daily/allow_list.json`. Each entry maps a table to the list of columns that are safe to copy with real values. Columns not listed will still exist in the dump, but they’ll be populated with fake data (or nulls) to satisfy constraints without leaking secrets.

0 commit comments

Comments
 (0)