<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Work on this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=441755) - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=441755) </details> <!--IssueSummary end--> MR: Pending <!-- The first line of the MR must be one of the following: 1. `MR: Pending` 2. `MR: <MR link with trailing +>`, and the first description line of the MR should be `Issue: <Issue link with trailing +>` 3. `MR: No MR` For more context, see: https://about.gitlab.com/handbook/engineering/development/dev/create/ide/index.html#1-to-1-relationship-of-issues-to-mrs --> <!-- The following sections should be filled out as part of the refinement process before the issue is prioritized. For more context, see: https://about.gitlab.com/handbook/engineering/development/dev/create/ide/#2-pre-iteration-planning-meeting --> ## Description This is created as a follow-up to the discussion in this [thread](https://gitlab.com/gitlab-org/remote-development/gitlab-remote-development-docs/-/merge_requests/44#note_1752809517). For some background, as a part of supporting group-agent authorization strategy, a decision was made to create a new field `remoteDevelopmentClusterAgents` under `group` query to list all the cluster agents with remote development support (with configurable filters). ```graphql group(fullPath: "gitlab-qa-sandbox-group-6") { id remoteDevelopmentClusterAgents(filter: DIRECTLY_MAPPED) { nodes { id name } } } ``` As a part of this discussion, another conclusion was reached to move the existing logic under the following graphql query resolver to the resolver for this new field. Since this new field is maintained by RD team, this migration would enabled greater control over this part of domain logic, as the current query resolver that returns all agents under a group is not maintained by RD team. ```graphql group(fullPath: $groupPath) { id clusterAgents(hasRemoteDevelopmentEnabled: true) { nodes { id name project { id nameWithNamespace } } } } ``` ## Acceptance Criteria - [ ] Existing dependency on `group.clusterAgents(hasRemoteDevelopmentEnabled: true)` in Remote Development code is replaced with with calls to `group.remoteDevelopmentClusterAgents`. Functionally speaking, `group.remoteDevelopmentClusterAgents` should have the contract as `group.clusterAgents(hasRemoteDevelopmentEnabled: true)` - [ ] Add specs to verify this change - [ ] Ensure all code/references/docs related to prior resolver logic in Cluster Agent domain is removed/deleted. ## Technical Requirements Same as acceptance criteria ## Design Requirements NA ## Impact Assessment NA ## User Story NA <!-- Replace with other type, e.g. bug or maintenance, if appropriate --> <!-- Replace with other subtype if appropriate --> <!-- By default, all issues start in the unprioritized status. See https://about.gitlab.com/handbook/engineering/development/dev/create/ide/#-remote-development-planning-process --> <!-- For simplicity and to avoid triage bot warnings about missing workflow labels, we will default to issues starting at the refinement phase -->