Actions
User Story #277
open
Epic #49: Implement user, groups and permissions management
Feature #265: Permission catalog
As a module author, I want my module to declare its own permissions when it connects, so that its features can be granted without changing the platform
User Story #277:
As a module author, I want my module to declare its own permissions when it connects, so that its features can be granted without changing the platform
Start date:
Due date:
% Done:
0%
Estimated time:
Description
A module brings capabilities the platform knows nothing about, such as restarting a Minecraft server. It declares them itself, under its own namespace, and they become available to role editors immediately.
Only modules declare permissions. A runtime running on an agent reports what it can deploy; the module that fronts that kind of server owns the permission names.
Acceptance criteria
- A module declares permission names, descriptions and applicable object kinds on connection
- Declared permissions appear in the catalog and in the role editor without a restart
- A module can only declare permissions inside its own namespace
- Re-declaring updates descriptions without disturbing existing roles or grants
- Malformed names are rejected with a clear reason
Rejection reason
Superseded by the rewritten epic #49
Updated by
Actions