Skip to content

v1.1.26 — quota alerts perspective + role read parity

Choose a tag to compare

View all tags
@yakari007 yakari007 released this 07 Jul 07:44
· 33 commits to master since this release
v1.1.26
d56f424
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

New

  • s3_quota_alerts_perspective — read-only perspective (GET /s3/quota-alerts-perspective), one row per S3 account currently at/above the 80% quota warning threshold (or already blocked) on storage or monthly egress. Uses the same thresholds as QuotaHelper/QuotaWarningNotification/QuotaExceededNotification, so it always reflects what did (or will) trigger an alert email.
    • Ships as a DB view — see schemas/s3_quota_alerts_perspective.sql for the CREATE OR REPLACE VIEW to apply to the database (no Laravel migration, same as the other schemas/*.sql references in this repo).
    • Full model/controller/service/transformer/request/filter scaffolding, mirroring the existing worm-expiring-perspective pattern.

Fix

  • S3UserRole was missing read access to s3_account_stats, s3_accounts_perspective, and s3_server_capacity_stats, even though S3ManagerRole/S3AdminRole already had them — brought to parity.
  • s3_quota_alerts_perspective:read granted to all three S3 roles (admin/manager/user).
Assets 2
Loading