Backend spike on the agent authorization policies at the group level
MR: !142270 (closed)
Description
Carry out a spike for supporting group-level mapping for remote development agents. The purpose is to fully evaluate the technical changes required. The spike effort can be formalized later (with feature flag etc) before it goes into production.
Acceptance Criteria
-
Spike should support listing of group-level mappings by the authorized users -
Spike should support updates to group-level mappings by the authorized users
Technical Requirements
- Same as acceptance criteria
Design Requirements
- There will be UI changes required for the full feature and can be reviewed by FE / designer before they make it to production. However, the purpose of the spike is to only verify the backend changes and see if they are good enough to support the requirements
Impact Assessment
NA
User Story
NA
Edited by Hunar Khanna