Installation
Metadata and artifact data layers
Define the separation, ownership, and validation boundaries of PostgreSQL and filesystem/S3 storage layers.
Data separation
Metadata, audit, and operation records live in PostgreSQL; artifact content lives in the selected storage component.
Operational requirement
The two data layers require consistent but separate backup, restore, capacity, health, and access plans.
Consistency model
PostgreSQL stores artifact ownership, state, checksum, size, and storage reference, while filesystem or S3 stores byte content. If the two layers are not reconciled at the same recovery point, missing metadata, orphan objects, or unavailable artifacts can result.
PostgreSQL plan
The target environment must document database version, TLS, credential source, Flyway migration permission, connection-pool budget, backup interval, and restore test. As replica count grows, multiply pool values per pod and retain headroom for administration and maintenance connections.
Storage plan
For S3, define bucket, region, endpoint and path-style behavior, credential rotation, object lifecycle, and capacity alerts. For filesystem, define shared mount, RWX semantics, inode and space monitoring, permissions, and archive directory.
- Every application replica seeing the same byte content for the same object key
- Health and readiness surfacing target-storage and PostgreSQL outages
- Joint validation of ingress, temporary-disk, and storage limits for large packages
- Source and target capacity plus rollback ownership for cleanup archive and storage transfer
Backup and restore boundary
A complete public runbook coordinating PostgreSQL, artifact storage, and raw SBOM data is not yet available. Before production approval, the organization must provide dated test evidence for write quiescence, snapshot order, secret or KMS access, restore reconciliation, and sample checksum validation.
Recovery acceptance criteria
After restore, reconcile repository and artifact counts, metadata state, storage references, checksums, and sample native-client downloads. Also verify task and audit history remains available and that new publish, scan, and cleanup operations work.