App Object Storage
Verfügbarkeit
Managed object storage ist noch nicht verfügbar. Current bucket service ist control-plane preview.
Creates bucket-shaped record, generates one-time S3-shaped credentials, kann OF_S3_* environment
variables publish, endpoint ist aber stub-minio-platform.local:9000. No MinIO bucket created und
no object can be stored there.
Use record with status stub nicht für uploads, backups oder data that must survive. Successful call
proves only control-plane contract ran.
Was Sie heute testen können
Preview exercises diese boundaries:
- unique bucket-name generation;
- app ownership checks in MCP wrapper;
- one-time secret handling;
- metadata-only list responses;
- publication of
OF_S3_ENDPOINT,OF_S3_BUCKET,OF_S3_ACCESS_KEY,OF_S3_SECRET_KEY,OF_S3_REGION; und - association of bucket reference with app.
If environment publication succeeds, values still placeholders. Remove before deploying workload expecting real storage.
MCP tools
| Tool | Current behavior |
|---|---|
add_app_bucket(app_id) | Creates stub record und may publish placeholder OF_S3_* values. |
list_app_buckets(app_id) | Lists metadata. Never returns secret key. |
add_app_bucket(app_id='550e8400-e29b-41d4-a716-446655440000')Response before using prüfen:
{
"bucket_id": "buk-a7f3b2c1d9e4f",
"endpoint_url": "http://stub-minio-platform.local:9000",
"status": "stub",
"env_published": false
}When automatic environment publication unavailable, response kann secret und env_payload once enthalten.
That does not turn stub endpoint into storage. Handle response as sensitive und do not log.
REST contract
| Method | Path | Result |
|---|---|---|
POST | /api/app-infra/buckets | Creates preview record und returns one-time credential-shaped data. |
GET | /api/app-infra/buckets/{bucket_id} | Returns metadata without secret key. |
GET | /api/app-infra/buckets?app_id={app_id} | Lists bucket metadata for app. |
Prefer owner-scoped MCP tools für normal use. Platform routes sind internal integration surface.
Planned application contract
When real provider enabled, applications construct S3-compatible client explicitly from five OF_S3_* variables.
Do not rely on ambient AWS credentials. Same variable names usable with temporary operator-managed S3 service today,
provided real values through App environment variables.
Before managed storage ready genannt werden kann
Production-capable release braucht evidence für:
- deployed reachable object-store host;
- per-app access isolation;
- upload, download und redeploy-persistence tests;
- rotation und safe deprovisioning;
- capacity, availability und error monitoring; und
- backup or replication behavior appropriate to stated durability target.
Until checks pass, operator-managed S3-compatible service nutzen und recovery path directly testen.