| 15 Nov 2022 |
 aciceri | Or more generally permissions management for for single jobsets | 10:39:54 |
| aciceri | Or even by project | 10:41:02 |
 das_j | I only know of the db table, I'm not aware of config in the frontend | 10:41:24 |
| aciceri | Do you mean that the table has a schema that captures these informations? | 10:42:00 |
| aciceri | I mean permissions per jobsets | 10:42:14 |
| das_j | hydra=# table projectmembers ;
project | username
---------+----------
(0 rows)
| 10:42:35 |
| das_j | that's the best I know | 10:42:45 |
| aciceri | does this mean that the a user cannot have different permissions o | 10:44:53 |
| aciceri | * does this mean that the a user cannot have different permissions for different projects? | 10:45:02 |
| aciceri | * does this mean that the an user cannot have different permissions for different projects? | 10:45:10 |
| das_j | I have no idea tbh | 10:45:29 |
| aciceri | Frankly I'm only interested into the restart-jobs role, I would like to have the same user able to restart jobs from jobsets from a project but not from another project | 10:46:28 |
| aciceri | I would like to manage these users (and which which jobsets they can restart) declaratively using an module option | 10:50:33 |
 @linus:schreibt.jetzt | sub mayRestartJobs {
my ($c, $project) = @_;
return
$c->user_exists &&
(isAdmin($c) ||
hasRestartJobsRole($c) ||
isProjectOwner($c, $project));
}
| 10:54:01 |
