feat: keep delivered work in S3-compatible object storage (ADR-0004 phase 3)
The store's rules now sit on a Blobs layer: a folder, as before, or a prefix in an S3-compatible bucket (MinIO locally), chosen by STORE_BACKEND. The layout is the same in both; the record is written last. - S3_BUCKET, S3_PREFIX, S3_ENDPOINT_URL, S3_REGION; AWS credentials - an s3 extra (boto3), installed in the image; moto for tests - every store test runs on both kinds of storage Retention, the platform's sign-in and each kept file as a platform artifact are left: the last needs the platform's S3 backend, which it does not yet have. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -5,8 +5,8 @@
|
||||
#
|
||||
# Which agents it routes to is configuration, mounted at /app/agents.yaml
|
||||
# (AGENTS_FILE); deploy/agents.local.yaml is the local KAB platform's. What agents
|
||||
# deliver is kept in /data/store (ADR-0004); give it a volume, a PUBLIC_URL and a
|
||||
# LINK_SECRET.
|
||||
# deliver is kept in /data/store (ADR-0004), or in an S3-compatible bucket with
|
||||
# STORE_BACKEND=s3; give it a volume or a bucket, a PUBLIC_URL and a LINK_SECRET.
|
||||
|
||||
FROM python:3.12-slim AS builder
|
||||
|
||||
@@ -14,7 +14,7 @@ WORKDIR /build
|
||||
COPY pyproject.toml ./
|
||||
COPY execution_engine/ ./execution_engine/
|
||||
COPY orchestration/ ./orchestration/
|
||||
RUN pip install --no-cache-dir --prefix=/install .
|
||||
RUN pip install --no-cache-dir --prefix=/install ".[s3]"
|
||||
|
||||
|
||||
FROM python:3.12-slim
|
||||
|
||||
Reference in New Issue
Block a user