Production checklist
Verify security, reproducibility, resilience, and observability before launch.
8 min Updated 2026-08-15Docs version 1.0 - 1Secure credentials
- 2Pin releases
- 3Test failure paths
- 4Monitor quality
In this guide
- 1Secure credentials
- 2Pin releases
- 3Test failure paths
- 4Monitor quality
Security
- 1
Use a production-only bearer key from a managed secret store
- 2
Redact Authorization from logs and traces
- 3
Use HTTPS and verify certificates
- 4
Define credential rotation and emergency revocation owners
Data contract
- 1
Validate required OpenAPI fields and enums
- 2
Persist dataset_id, release_id, dataset_version, and quality_status
- 3
Define whether partial releases are accepted
- 4
Preserve identity_fields during reconciliation
- 5
Archive required release provenance
Resilience
- 1
Set connection and total deadlines
- 2
Respect Retry-After on 429
- 3
Use exponential backoff with jitter for safe retries
- 4
Reconcile ambiguous build creation before resubmitting
- 5
Stream downloads to temporary storage
Observability
- 1
Track success, latency, 4xx, 429, and 5xx separately
- 2
Log request_id and stable resource IDs
- 3
Alert on partial releases and broken lineage
- 4
Monitor build age by status
- 5
Exercise sandbox and failure tests before each integration release