Launch blocker: validate the release candidate on real AWS S3 with end-to-end Git hosting
I maintainer di solito rispondono entro 1 giorno
@ThomasK33 ci sta già lavorando.
Dal 11/9/2026.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
Launch gate
Before the public open-source launch and Show HN announcement, record a reproducible real-AWS validation of the release candidate. SeaweedFS and Floci provide valuable regression coverage, but they do not establish that AWS authentication, permissions, storage behavior, and the complete Git hosting flow work together in the intended deployment.
Existing evidence and remaining gap
This is not the first AWS test. The recorded S3 campaign from August 27, 2026 passed the 22-surface qualification suite and exercised real Git pushes and recovery against S3. It was a single-day campaign from compute outside AWS and predates subsequent changes.
The testing reference documents emulator gaps: the pinned Floci lane does not enforce S3 IAM policy decisions or fully validate header-auth signatures/session tokens. Its passing Git/LFS suite therefore cannot prove those AWS properties.
The existing S3-only backend promotion tracker owns experimental-to-supported criteria, including pending contention reruns and multi-day measurements. This issue owns the product-wide public-launch AWS validation; it does not promote S3-only storage or replace that tracker.
Acceptance criteria
- Define an isolated AWS sandbox, dedicated scratch resources, region, least-privilege test role, spending limit, and reliable teardown before provisioning. Use short-lived credentials and retain no secrets in evidence.
- Pin the exact release candidate commit and binary/container artifact. Provide reproducible setup and test commands, preferably automated, with logs and a clear pass/fail report.
- Run from EC2 in the same AWS region as the test bucket. Cover the standard Postgres + S3 topology, including two server replicas; separately exercise the advertised experimental single-node S3-only mode and keep its status explicit.
- Verify repository creation and API reads/writes, Git clone/fetch/push, branches/tags, authorization denials, Git LFS uploads/downloads, and agreement between API and Git views. Verify that writes through one standard-mode replica can be read through the other.
- Test AWS-specific behavior that emulators cannot establish: valid and invalid temporary credentials, session-token handling/refresh, denied IAM permissions, expected bucket owner, valid/tampered presigned URLs, and the conditional-write semantics used by S3-only storage.
- Exercise concurrent writes, cold-cache restart, interrupted push/recovery, and the existing S3-only qualification and lease/restart drills on real S3. Verify acknowledged repository data remains readable and report any failed or skipped case explicitly. Link remaining S3-only promotion criteria to the existing tracker.
- If Kubernetes/EKS is part of the launch support claim, add a focused deployment smoke covering workload identity, ingress/TLS, pod replacement, and rollout behavior. Otherwise record EKS as a follow-up rather than a prerequisite for proving S3 compatibility.
- Publish the evidence and supported deployment limits, resolve release-blocking failures, and verify resource teardown. Close this launch blocker only when the release candidate has the required evidence.
Scope
Keep emulator CI coverage. Real AWS testing supplements it. This issue tracks readiness; it does not authorize provisioning resources, incurring cloud spend, changing repository visibility, or publishing a release.
- Lingua principale
- Go
- Stelle
- 0
- Fork
- 0
- Merge medio
- 6h 16m
- PR unite (30g)
- 243
Preparare l'ambiente
- Include un Dockerfile o un file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di coder/openstorage
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
coder/openstorage#807 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 49/100
coder/openstorage#806 ·
I maintainer di solito rispondono entro 1 giorno
-
api: merge/preview ignores strategy, squash and allow_unrelated_historiesForse già presa @ThomasK33 l’ha presa oggi. Aperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
coder/openstorage#805 ·
I maintainer di solito rispondono entro 1 giorno
-
githttp: +import remote serves clone and fetch, and its pushes stay out of the normal branch listForse già presa @ThomasK33 l’ha presa oggi. Aperta
Difficoltà 5/5 Più di una settimana Idoneità per principianti 20/100
coder/openstorage#804 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
api: branches/create ignores expected_target_sha, so a guarded create or move can overwrite a branchForse già presa @ThomasK33 l’ha presa oggi. Aperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
coder/openstorage#803 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di coder/openstorage
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 86/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
coder/coder-logstream-kube#255 · 1 commento ·
-
kind/features
Difficoltà 2/5 1-3 ore Idoneità per principianti 73/100
TencentBlueKing/bk-nodemgr#3991 ·
I maintainer di solito rispondono entro 1 giorno
-
meta
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
last9/last9-mcp-server#554 ·
I maintainer di solito rispondono entro 1 giorno