Drop the bingo photo migration from minio-init
All checks were successful
Deploy storage stack / deploy (push) Successful in 18s
All checks were successful
Deploy storage stack / deploy (push) Successful in 18s
All photos are in datacenterbingo-photos and both apps use it, so stop mirroring from asxpio-invoices/bingo/ and take away the bingo user's read access there. Assisted-by: Claude:opus-5
This commit is contained in:
parent
63283b1c47
commit
c849e253f9
2 changed files with 5 additions and 11 deletions
|
|
@ -64,8 +64,7 @@ can connect.
|
|||
These are read-only:
|
||||
- Role `bingo` gets SELECT on `bingo_datacenters` and `bingo_incidents` in
|
||||
the `asxpio` DB, and `default_transaction_read_only`.
|
||||
- The MinIO user may only `GetObject` in the `datacenterbingo-photos` bucket
|
||||
(and, until the migration is cleaned up, under `asxpio-invoices/bingo/`).
|
||||
- The MinIO user may only `GetObject` in the `datacenterbingo-photos` bucket.
|
||||
asxpio's user has read-write on that bucket for the admin's uploads.
|
||||
|
||||
The same values go on the **datacenterbingo repo**.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue