Strategies to Edit Production Data
summary
Five concrete strategies from raw SQL to a built Script Runner service compare tradeoffs: a Google spreadsheet audit trail gives immediate logging with almost no setup; local Python scripts add reusability but lose persistent logs; running on an existing server or a Jenkins task runner enables long jobs but can hog resources; a hosted Script Runner centralizes credentials, enforces code review, scales for operations that once touched 50 million products and proves to be the most auditable and user friendly.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:30Why We Edit Production Data
- 5:59Develop a Review Process for Manual Edits
- 7:161. Add record to a spreadsheet 2. Reviewer approves the query
- 10:53Run Scripts Locally
- 14:42Run Scripts on an Existing Server
- 19:13Use a task runner
- 23:51Build a Script Runner Service
related talks
30mStrategies to Edit Production Data
27mStrategies to Edit Production Data
29mStrategies To Edit Production Data
26mStrategies to Edit Production Data
30mReliable Data Processing with Minimal Toil
25mOptimize your Data Pipeline without Rewriting it
38mData Secrets from a Platform Engineer
21mPractical Deployment Strategies for Production Python Apps