| Summary: | [RFE] Allow task updates to be limited to particular users or groups | ||
|---|---|---|---|
| Product: | [Retired] Beaker | Reporter: | Nick Coghlan <ncoghlan> |
| Component: | scheduler | Assignee: | beaker-dev-list |
| Status: | CLOSED WONTFIX | QA Contact: | tools-bugs <tools-bugs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 0.14 | CC: | cbouchar, qwan, tools-bugs |
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-11-13 19:27:37 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
It should be possible to build something similar to the system ACL model, with just two levels of access: - upload new versions - edit the policy |
Currently, all users of a given Beaker installation can update any task uploaded to the task library. This includes the core tasks that Beaker relies on for correct operation of various features: /distribution/install /distribution/reservesys /distribution/inventory /distribution/updateDistro /distribution/virt/install /distribution/virt/start To prevent erroneous updates to these tasks (and other tasks), it should be possible to limit updates to a given task to a specific set of users or groups (similar to a cut down version of system access policies).