Because riverui is unauthenticated right now and has no permissions checks for users, I've opted to use it with a read-only Postgres user in our deployment to avoid accidentally cancelling or restarting running jobs. This user can read the state of all jobs, but cannot modify any.
This works fine to display jobs, but any modifying action returns a 500 right now. It would be better if riverui could return a more descriptive error in that case.
Because
riverui
is unauthenticated right now and has no permissions checks for users, I've opted to use it with a read-only Postgres user in our deployment to avoid accidentally cancelling or restarting running jobs. This user can read the state of all jobs, but cannot modify any.This works fine to display jobs, but any modifying action returns a 500 right now. It would be better if riverui could return a more descriptive error in that case.