Skip to content

Draft: Drop the editor feild from the workspaces table

Daniyal Arshad requested to merge da-remove-editor-field-from-workspaces-table into master

Issue: Drop editor field in workspaces table as it is ... (#486301)

What does this MR do and why?

As a follow up to Add ignore rule for editor field, this MR drops the editor field from the workspaces table in the M+1 release.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Acceptance Criteria

  • Migration to drop editor column
  • Create follow up MR in release M+2 for removing the ignore rule

Follow up MR: Draft: Remove ignore rule for editor field on w... (!167825)

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

This MR does not contain any UI changes

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

  • Setup workspaces locally following this guide
  • Checkout this branch and run the migration rails db:migrate:main in the terminal
  • Navigate to http://gdk.test:3000/-/remote_development/workspaces/ and create a new workspace
  • In rails console or any SQL client check that the new workspace has been created & that the editor field does not exist anymore
  • Make sure the workspace is correctly provisioned and has the Running status, open the workspace from the Preview url and test to make sure that the VS Code fork loads without issues
  • Optional: Run some commands in the terminal in the workspace to make sure everything is working
  • Finally terminate the workspace to ensure that it is stopped without any issues.
Edited by Daniyal Arshad

Merge request reports