Simplify permission checking on template level #49562
Labels
No Label
legacy project
Infrastructure: Websites
legacy project
Pillar
legacy project
Pillar Framework
legacy project
Pillar Website
Priority::High
Priority::Low
Priority::Normal
Status::Archived
Status::Confirmed
Status::Resolved
Type::Bug
Type::Design
Type::Patch
Type::Report
Type::To Do
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: archive/pillar#49562
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Templates now have quite complex
if
-conditions for permission checking. We might want to simplify this using a notion of "capabilities" that map to groups & allowed methods.Changed status to: 'Open'
Added subscribers: @dr.sybren, @pablovazquez, @fsiddi
Changed status from 'Open' to: 'Resolved'
Capablities have been implemented.