dbd45a72c3
if the user/token could have either configured/manually executed the task, but it was either executed via the schedule (root@pam) or another user/token. without this change, semi-privileged users (that cannot read all tasks globally, but are DatastoreAdmin) could schedule jobs, but not read their logs once the schedule executes them. it also makes sense for multiple such users to see eachothers manually executed jobs, as long as the privilege level on the datastore (or remote/remote_store/local store) itself is sufficient. Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com> |
||
---|---|---|
.. | ||
command_socket.rs | ||
config.rs | ||
email_notifications.rs | ||
environment.rs | ||
formatter.rs | ||
gc_job.rs | ||
h2service.rs | ||
jobstate.rs | ||
prune_job.rs | ||
report.rs | ||
rest.rs | ||
state.rs | ||
upid.rs | ||
verify_job.rs | ||
worker_task.rs |