Repository navigation
·
4929 commits
to 07727160428bee2f03d616360906fb4b579c9b7c
since this release
0.3.2 - 2026-11-13
Added
- Add deployment-lockable switches for RGW Accounts, RGW Users, Shared S3 Connections, and Private S3 Connections, with migration-safe defaults and consistent Admin, onboarding, execution-context, and navigation gating.
- Add an automatic Manager Browser data-access policy with platform and resource-level inheritance for Accounts and RGW Users, while preserving explicit per-association grants and access-audit provenance.
Changed
- Centralize deployment-owned runtime configuration in a versioned
DEPLOYMENT_CONFIGmanifest, with localRUNTIME_SURFACES, deployment locks, endpoint adoption, and Compose/Helm provisioning support. - Validate Portal server access-log advanced-filter scalar/list/null value shapes at the API boundary and remove unreachable matcher fallbacks.
- Validate Ceph Admin account and user advanced-filter field/operator/value shapes at the API boundary and remove unreachable identity-listing enrichment branches.
- Validate shared Ceph Admin and Storage Ops advanced bucket filter rules against the exact field/operator/value-shape contract, removing matcher fallbacks for malformed field and feature-parameter rules.
- Validate shared Ceph Admin and Storage Ops bucket listing sort fields and UI-tag match mode at the API boundary, removing silent runtime fallback to name sorting or
anytag matching. - Tighten Ceph Admin account and user listing sort fields to the exact fields exposed by the bundled frontend, removing the retired account
namesort alias and silent fallback for unknown fields. - Canonicalize Storage Endpoint credential replacement so Admin, Runtime, Supervision, and Ceph Admin identities all reuse a stored pair only when both edit fields are blank, and require both fields for an explicit replacement.
- Simplify the internal Admin MFA reset route to return
204 No Content; removal counters and passkey-policy state remain recorded in the security audit instead of being duplicated in an unused response body. - Keep bucket-composition policy descriptions inline in General Settings and improve collapsible sidebar hierarchy and expansion behavior.
Fixed
- Preserve the Portal execution surface when standalone Browser favorites target Portal Storage Spaces, avoiding incorrect Browser-context revalidation failures.
- Mount deployment provisioning credential files into one-shot Compose provisioners so referenced secret files remain usable without embedding credentials in
DEPLOYMENT_CONFIG. - Build frontend static assets on the native BuildKit builder platform while retaining target-platform nginx runtimes, avoiding unnecessary ARM emulation during multi-architecture builds.
Upgrade notes
- Apply the normal Alembic upgrade path before starting the matching backend. Migrations
0263through0274tighten retained-reference foreign keys and cascades, add deployment configuration and managed-resource feature switches, and persist Manager Browser data-access policy state. - Breaking deployment change: move
FEATURE_*_ENABLEDandENV_STORAGE_ENDPOINTSto localRUNTIME_SURFACESand a versioned deployment manifest. Apply the deployment configuration migration before restarting existing Admin and User pools. - Deploy the matching backend and bundled frontend together because Portal server access-log advanced filters now reject invalid scalar/list/null value shapes instead of silently evaluating malformed rules. No database migration is required.
- Deploy the matching backend and bundled frontend together because Ceph Admin account/user advanced filters now reject unsupported field/operator combinations and invalid scalar/list/null value shapes instead of silently evaluating malformed rules. No database migration is required.
- Deploy the matching backend and bundled frontend together because shared Ceph Admin/Storage Ops advanced bucket filters now reject unsupported field/operator combinations and invalid scalar/list/null value shapes instead of silently evaluating malformed rules. No database migration is required.
- Deploy the matching backend and bundled frontend together because shared Ceph Admin/Storage Ops bucket listings now reject unknown
sort_byandui_tag_matchvalues instead of silently normalizing them. No database migration is required. - Deploy the matching backend and bundled frontend together because Ceph Admin account/user listings now reject unknown
sort_byvalues; useaccount_nameinstead of the retired accountnamealias. No database migration is required. - Deploy the matching backend and bundled frontend together because Storage Endpoint feature detection and onboarding no longer support the historical Admin access-key-only edit fallback. No database migration is required.
- Deploy the matching backend and bundled frontend together because Admin MFA reset now returns
204 No Contentinstead of an unused result object. No database migration is required.
Full changelog: v0.3.1...v0.3.2