rikrdo/arnes
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

F-003 fix: Sanitize SQL dump for safe dev use

Browse Source
This commit is contained in:
rikrdo
2026-05-25 08:14:34 +02:00
parent 3d41579ad3
commit e6feea5ee6
24 changed files with 483 additions and 1187942 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
spec/bdd/features/data/sanitized-sql-baseline.feature Normal file
View File

@@ -0,0 +1,18 @@
@F-003 @smoke @security @regression
Feature: Safe SQL baseline exists for legacy module development
As a maintainer
I want a tracked SQL baseline without sensitive live data
So I can develop locally without keeping a raw production snapshot in git
Scenario: Tracked SQL baseline is sanitized
Given the repo contains one tracked SQL baseline for the legacy module
When feature F-003 is applied
Then the tracked SQL baseline does not contain customer or live order snapshot data
And the baseline contains only safe schema and synthetic seed data needed for local module work
Scenario: Local private data handling is documented
Given a maintainer may still need a private raw dump outside git
When feature F-003 is applied
Then the repo documents where private local data should live
And the tracked SQL baseline remains safe for commit and push