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 The following discussion from !125331 should be addressed: - [ ] @cwoolley-gitlab started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/125331#note_1464756165): > **issue (non-blocking)** We should revisit these route definitions, so that they only expose what we actually need. > > Currently, what we have here adds several routes that we don't use. Here's the output of `bin/rails routes`: > > ``` > remote_development_workspace_workspaces GET /-/remote_development/workspaces(/*vueroute)/:workspace_id/workspaces(.:format) remote_development/workspaces#index > new_remote_development_workspace_workspace GET /-/remote_development/workspaces(/*vueroute)/:workspace_id/workspaces/new(.:format) remote_development/workspaces#index > remote_development_workspaces GET /-/remote_development/workspaces(/*vueroute)(.:format) remote_development/workspaces#index > POST /-/remote_development/workspaces(/*vueroute)(.:format) remote_development/workspaces#create > new_remote_development_workspace GET /-/remote_development/workspaces(/*vueroute)/new(.:format) remote_development/workspaces#new > edit_remote_development_workspace GET /-/remote_development/workspaces(/*vueroute)/:id/edit(.:format) remote_development/workspaces#edit > remote_development_workspace GET /-/remote_development/workspaces(/*vueroute)/:id(.:format) remote_development/workspaces#show > PATCH /-/remote_development/workspaces(/*vueroute)/:id(.:format) remote_development/workspaces#update > PUT /-/remote_development/workspaces(/*vueroute)/:id(.:format) remote_development/workspaces#update > DELETE /-/remote_development/workspaces(/*vueroute)/:id(.:format) remote_development/workspaces#destroy > > ``` > > Let's create a follow-up backend issue to address cleaning this up. ## Acceptance Criteria TODO: Fill out (required) - [ ] [Describe what must be achieved to complete this issue.] - [ ] [Describe another requirement needed to complete this issue.] - [ ] [Add additional acceptance criteria as needed.] ## Technical Requirements TODO: Fill out or delete [If applicable, please list out any technical requirements for this feature/enhancement.] ## Design Requirements TODO: Fill out or delete [If applicable, please provide a link to the design specifications for this feature/enhancement.] ## Impact Assessment TODO: Fill out or delete [Please describe the impact this feature/enhancement will have on the user experience and/or the product as a whole.] ## User Story TODO: Fill out or delete [Provide a user story to illustrate the use case for this feature/enhancement. Include examples to help communicate the intended functionality.] <!-- 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 -->