F-003 fix: Sanitize SQL dump for safe dev use
This commit is contained in:
@@ -116,6 +116,41 @@
|
||||
"security": false,
|
||||
"qa": false
|
||||
}
|
||||
},
|
||||
{
|
||||
"id": "F-003",
|
||||
"type": "fix",
|
||||
"title": "Sanitize SQL dump for safe dev use",
|
||||
"problem": "Repo keeps production-like SQL dump with sensitive data risk",
|
||||
"goal": "Keep dev database baseline without sensitive live data in repo",
|
||||
"scope_in": [
|
||||
"review dump scope",
|
||||
"define safe replacement strategy",
|
||||
"remove or redact sensitive data",
|
||||
"document local data handling"
|
||||
],
|
||||
"scope_out": [
|
||||
"No app logic change",
|
||||
"No production DB changes",
|
||||
"No schema redesign"
|
||||
],
|
||||
"priority": "high",
|
||||
"risk": "high",
|
||||
"description": "Problem: Repo keeps production-like SQL dump with sensitive data risk. Goal: Keep dev database baseline without sensitive live data in repo. Scope IN: review dump scope, define safe replacement strategy, remove or redact sensitive data, document local data handling. Scope OUT: No app logic change, No production DB changes, No schema redesign. Type: fix. Priority: high. Risk: high.",
|
||||
"acceptance": [
|
||||
"Repo no longer stores raw sensitive production-like SQL dump as current dev baseline",
|
||||
"Safe dev data handling is documented",
|
||||
"Replacement dump or import path keeps local development possible",
|
||||
"Security risk note for SQL data is addressed",
|
||||
"verify.sh is green"
|
||||
],
|
||||
"status": "done",
|
||||
"created_at": "2026-05-25",
|
||||
"gates": {
|
||||
"review": false,
|
||||
"security": false,
|
||||
"qa": false
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user