OWASP / OWASP/OpenCRE

Continuity runbook: Catalog import and sync

Open
#1,068 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

existing-maintainers-only
Dominant language
Python
Stars
180
Forks
137
Avg merge
3d 23h
Merged PRs (30d)
21

Description

Task

A second maintainer can refresh the catalog locally (make import-all) and, only with extra approval, sync selected tables to Heroku — never import against production DATABASE_URL.

Success criteria

  • Knows import is local-only (scripts/import-all.sh via Makefile)
  • Knows full scripts/db/sync-local-to-opencreorg.sh with SYNC_TABLES=all DROP SCHEMA public and requires the destructive confirmation phrase
  • Prefers --table flags for prod sync
  • Runbook docs/continuity/runbooks/catalog-import-and-sync.md (skill continuity-catalog-import-and-sync)

Context

  • AGENTS.md imports + production DB sections
  • After a prod table sync, run production-health (HTTP), not GA compute on Heroku

Constraints

  • existing maintainers only
  • Do not run Part B (prod sync) in this ticket’s first drill unless a maintainer names tables
  • No secret dumps

Agent prompt

See Agent prompt in docs/continuity/runbooks/catalog-import-and-sync.md.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with AGENTS.md and inspect the Makefile, scripts/import-all.sh, and scripts/db/sync-local-to-opencreorg.sh. Read the target runbook at docs/continuity/runbooks/catalog-import-and-sync.md, then verify it documents local-only imports, approved table selection, destructive confirmation, and production-health checks without exposing secrets.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
databases, devops, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.