Skip to navigation

November 18, 2026

Public API 0.13.0: no single call wipes a bucket or a registry

The public API manages resources. Files and container images stay on each product’s own endpoint, with the clients that already exist for them: S3 tools at <workspace>.blob.ibeestorage.com for Object Storage, and docker at registry.ibee.ai for Container Registry.

Removed: calls that delete everything in one go. One call could permanently delete every file in a bucket or every image in a registry, with no way back, by mistake or by misuse.

  • The empty-bucket job calls: POST and GET /object-storage/buckets/{bucket_name}/empty-jobs, GET …/empty-jobs/{operation_id} and POST …/empty-jobs/{operation_id}/cancel.
  • POST /container-registry/registries/{registry_id}/empty.

Delete files with an S3 tool and images with docker or the repository and image delete calls, then delete the bucket or registry. The portal keeps its own empty buttons.

Removed: GET /container-registry/registries/{registry_id}/security/sboms/{artifact_digest}/download. Listing and reading SBOMs stay.

Changed: DELETE /object-storage/buckets/{bucket_name} now says what it does: it deletes an empty bucket, and a bucket that still holds files is refused with 409.

The active reference has 219 operations.