Stop performing database dump anonymisation in lower environments #3655
Description
User Need
As a database backup and restore procedure
I don't want to perform the anonymisation process outside of production
so that I'm not duplicating effort on database dumps that are already anonymised
What’s Needed
List anything the solution must do or be (behaviour, performance, security, UX, etc.).
- Stop performing database dump anonymisation in staging and integration
- Continue writing out the database dumps, so that they are available for developers to use in their work
Acceptance Criteria
Clear, measurable conditions to verify the story is complete and valuable.
- Database dump anonymisation happens in production only