Currently Beaker has an undocumented feature where users in the special group 'queue_admin' are permitted to change the priority of any job. But: * it should be documented * it should be set up by default (currently beaker-init does not create the group) * it should use a proper TG permission, in the same style as 'secret_visible', instead of hard-coding the group name Converting it to a permission needs to be done in a backwards-compatible way. Namely an existing 'queue_admin' group should be granted the new permission. Once it is using a permission, we can remove the special protections which prevent renaming the 'queue_admin' group.
Found an old patch I wrote for this last year...
https://gerrit.beaker-project.org/5968
This can go to 26.0, no need to make the 25.0 release even bigger at this point.
I accidentally just merged this for 25.0, forgetting that I was going to hold off until 26.0 to avoid making 25.0 even bigger.
The new permission is called 'change_prio'. Suggested steps to verify: 1. Check the docs for it make sense... 2. As a Beaker admin, create a new group, give the group 'change_prio' permission, add an otherwise unprivileged user to the group. 3. Submit a job to Beaker. 4. While the job is queued, as the unprivileged user go to the job page and adjust its priority up or down.
Verified that * the docs for it make sense * the user "unprivileged" (part of group "queue_admin_test" with change_prio permission) could successfully bump priority of a job (not created by unprivileged) up or down
Beaker 25.0 has been released. Release notes are available upstream: https://beaker-project.org/docs/whats-new/release-25.html