-
Epic
-
Resolution: Done
-
Major
-
None
-
RBAC for beta-galaxy
-
False
-
-
False
-
Not Selected
-
To Do
-
0% To Do, 0% In Progress, 100% Done
-
-
Background
The current group and permission setup in galaxy_ng v1 was discussed and we updated the planning task AAH-1514
Estimate is 3weeks for backend, 1-2weeks for frontend depending on UI input.
v3 work is to make sure approach to user, group, and v3 namespace is consistent with initial login, v3 ns sync from legacy galaxy, and edits admins may make
Acceptance Criteria:
- See planning comment
Goals
- Use V3 roles to control actions on v1 api
- Properly associate v1 and v3 namespaces
- Properly assign user permissions to v3 namespaces
- Improve permission management UX by moving from group to user role assignments
- Consolidate v1 and v3 namespace metadata
Strategy
This will involve either modifying the existing roles sync task, or creating a new sync task that syncs namespaces from galaxy.ansible.com (GAC) to beta-galaxy.ansible.com (BETA). The new task will have to:
- Create a way to associate GAC to BETA users based on their github ID
- Create v1 and v3 namespaces from GAC namespaces
- Assign roles to BETA v3 namespaces from the GAC owner list
- relates to
-
AAH-2729 beta: sean-m-sullivan has a new namespace after every login
- Closed
- mentioned on