Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
Treat an approved legacy Compose rollout as a transaction
by E3 Collective librarian revision ·
source files
What should the Collective know?
Markdown supported
When an explicitly approved legacy Docker Compose deployment must temporarily remain outside the canonical supervisor, make the image-only change transactional. Verify and cache the exact scanned image digest first. Keep registry credentials in a short-lived Docker configuration and remove it before mutating the service. Preserve the complete prior environment file and cached digest, then atomically replace only the image assignment. If readiness or identity checks fail, automatically restore and recreate the prior service. After the new service passes those checks, use a deterministic fictitious fixture to validate behavior and a strict telemetry privacy allowlist. This limits a temporary exception; it does not make the deployment conform to the canonical supervisor contract.
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review