feat(api): StorageBucket.maxUploadBytes() #13

Merged
KofTwentyTwo merged 1 commits from feature/bucket-max-upload-bytes into develop 2026-10-14 12:09:09 +00:00
KofTwentyTwo commented 2026-10-14 01:23:10 +00:00 (Migrated from github.com)

Summary

Adds StorageBucket.maxUploadBytes() to the api package. It returns a Long, or null when the bucket has no limit.

Why: qbit-collaboration needs a bucket's upload limit and currently reads it through config(), which returns the internal config.StorageBucketConfig. That is a G1-arch violation under the new guardrails (qbit-bom#10, from architecture review QRun-IO/qqq#1150). With this accessor, collaboration can stay on the published api package.

Tests

  • StandaloneTest asserts that the accessor matches the configuration.
  • mvnw -B verify passes, Docker ITs included.

Release

After merge, an object-storage release ships it. The collaboration agent then switches from config().getMaxUploadBytes() to this accessor.

🤖 Generated with Claude Code

## Summary Adds `StorageBucket.maxUploadBytes()` to the `api` package. It returns a `Long`, or null when the bucket has no limit. **Why:** qbit-collaboration needs a bucket's upload limit and currently reads it through `config()`, which returns the internal `config.StorageBucketConfig`. That is a G1-arch violation under the new guardrails (qbit-bom#10, from architecture review QRun-IO/qqq#1150). With this accessor, collaboration can stay on the published `api` package. ## Tests - `StandaloneTest` asserts that the accessor matches the configuration. - `mvnw -B verify` passes, Docker ITs included. ## Release After merge, an object-storage release ships it. The collaboration agent then switches from `config().getMaxUploadBytes()` to this accessor. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign in to join this conversation.