Server Publish #3

New issue

Open

opened 2026-02-07 14:04:21 +00:00 by Toasterson · 0 comments

Toasterson commented

2026-02-07 14:04:21 +00:00

(Migrated from codeberg.org)

Maintainer decisions — 2026-09-22

Deferred beyond v1 by the maintainer: local ingestion suffices, and CI will deliver a completed multi-package .p5p and notify an import script (#38). Authenticated REST publishing, its OIDC/RBAC decisions and provider provisioning are not v1 release gates. Preserve this ticket and its research/dependencies for later work; no later milestone was selected. Do not provision credentials or an identity provider as part of v1.

These decisions supersede conflicting earlier scope below. This update records maintainer decisions, not implementation or test completion.

Earlier brief and context

A Publish REST API where we can upload new packages. Should support uploading a p5p archive with multiple packages a zip file with multiple packages and upload packages by uploading manifests and files separately to the endpoints. All Uploads must happen within a transaction but of course clients can upload multiple archives or packages during one transaction. A transaction tracks which files it still needs based on the manifests uploaded and provides that info to the client both in responses and via REST endpoint should a client crash during a transaction. This way a transaction can be resumed. After a Transaction is commited the Repository is updated Atomically from the uploaded packages.

## Maintainer decisions — 2026-09-22 Deferred beyond v1 by the maintainer: local ingestion suffices, and CI will deliver a completed multi-package .p5p and notify an import script (#38). Authenticated REST publishing, its OIDC/RBAC decisions and provider provisioning are not v1 release gates. Preserve this ticket and its research/dependencies for later work; no later milestone was selected. Do not provision credentials or an identity provider as part of v1. These decisions supersede conflicting earlier scope below. This update records maintainer decisions, not implementation or test completion. <details> <summary>Earlier brief and context</summary> A Publish REST API where we can upload new packages. Should support uploading a p5p archive with multiple packages a zip file with multiple packages and upload packages by uploading manifests and files separately to the endpoints. All Uploads must happen within a transaction but of course clients can upload multiple archives or packages during one transaction. A transaction tracks which files it still needs based on the manifests uploaded and provides that info to the client both in responses and via REST endpoint should a client crash during a transaction. This way a transaction can be resumed. After a Transaction is commited the Repository is updated Atomically from the uploaded packages. </details>