BE: Remove feature flag from mutation APIs in the new group-agent authorization strategy
MR: !151720 (merged)
Description
As discussed in the Slack thread, we want the early adopters to be able to configure group-agent mapping even before they can use the new agent exposure strategy. This is not currently possible as the feature flag currently controls access for all the new authorisation strategy APIs. This means that once the feature flag is turned on, there will be a period during workspace usage will be limited until the cluster admins/owners have configured group-agent mappings and this can be disruptive to existing workspace users.
This can be addressed by removing the feature flag checks in the mutation APIs and have them restricted to the query APIs only.
Acceptance Criteria
-
Remove feature flag from the mutation APIs
Technical Requirements
Same as the technical requirements
Design Requirements
NA as this is exclusively a BE change
Impact Assessment
While users may be able to use the new group-authorisation APIs, the data that is written will not be used until the feature flag is turned on.
User Story
NA as this is exclusively a BE change