public/docs
6
0
Fork 0
Code Issues Pull requests Activity

docs: operate digest-pinned S3 enclave components #39

Closed
caution-bot wants to merge 1 commit from docs/s3-prebuilt-components into main
pull from: docs/s3-prebuilt-components
merge into: public:main
Conversation 1 Commits 1 Files changed 2 +102
caution-bot commented 2026-10-04 23:35:37 +00:00 (Migrated from codeberg.org)
Copy link

Summary

Companion runbook for https://codeberg.org/caution/platform/pulls/468, narrowed to enclave-component reuse rather than platform service management.

  • Document automatic component publication/pinning through make up, immutable API-image/component selection, explicit source fallback, bucket/IAM boundaries, and accepted-lock cold/warm behavior.
  • Remove full-platform release records, launcher/drop-ins, activation/recovery journal and make recover-release instructions. Existing Make/systemd owns service lifecycle; only the API consumes components.env.
  • Keep provenance, historical source reproduction and coordinated CLI/provisioner compatibility requirements. Explain normal operator recovery without promising database rollback or garbage collection.

One signed commit: a34ef2b36743494773bb8257baa2b638edeb829c on c1e97a0bb6e633042cfae5994eee5dac0f78e95a.

Test plan

On a fresh role-free disposable development-account EC2 host, from a hash-verified clean checkout of exactly this documentation commit:

make build-prod
  • Production image built successfully using the repository Dockerfile.
  • Ran that image with its HTTP listener bound only to 127.0.0.1; /reference/s3-prebuilt-components/ returned HTTP 200, with the new component-only instructions and no obsolete controller/recovery command references. Test container removed afterward.
  • git diff --check passed; checked reference consistency against the narrowed platform candidate 2d10813b95cca56f1927f0232381a7146c5cbcf3.

No documentation deployment and no dev service restart occurred. No new S3/IAM or Nitro acceptance is claimed by this docs build. Historical platform evidence remains bound to the commits on which it ran.

## Summary Companion runbook for https://codeberg.org/caution/platform/pulls/468, narrowed to enclave-component reuse rather than platform service management. - Document automatic component publication/pinning through `make up`, immutable API-image/component selection, explicit source fallback, bucket/IAM boundaries, and accepted-lock cold/warm behavior. - Remove full-platform release records, launcher/drop-ins, activation/recovery journal and `make recover-release` instructions. Existing Make/systemd owns service lifecycle; only the API consumes `components.env`. - Keep provenance, historical source reproduction and coordinated CLI/provisioner compatibility requirements. Explain normal operator recovery without promising database rollback or garbage collection. One signed commit: `a34ef2b36743494773bb8257baa2b638edeb829c` on `c1e97a0bb6e633042cfae5994eee5dac0f78e95a`. ## Test plan On a fresh role-free disposable development-account EC2 host, from a hash-verified clean checkout of exactly this documentation commit: ```sh make build-prod ``` - Production image built successfully using the repository Dockerfile. - Ran that image with its HTTP listener bound only to `127.0.0.1`; `/reference/s3-prebuilt-components/` returned HTTP **200**, with the new component-only instructions and no obsolete controller/recovery command references. Test container removed afterward. - `git diff --check` passed; checked reference consistency against the narrowed platform candidate `2d10813b95cca56f1927f0232381a7146c5cbcf3`. No documentation deployment and no dev service restart occurred. No new S3/IAM or Nitro acceptance is claimed by this docs build. Historical platform evidence remains bound to the commits on which it ran.
anton commented 2026-10-19 20:11:03 +00:00
Owner
Copy link

Superseded by #43, the unified release documentation update. It consolidates this proposal with the other open docs updates and corrects the combined guidance against platform main 2dd613e3.

Closing this PR to keep one review/release path. The original branch is retained; the replacement is not merged.

Superseded by #43, the unified release documentation update. It consolidates this proposal with the other open docs updates and corrects the combined guidance against platform main `2dd613e3`. Closing this PR to keep one review/release path. The original branch is retained; the replacement is not merged.
anton closed this pull request 2026-10-19 20:11:03 +00:00

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
public/docs!39
No description provided.