feat: Create Remote Scanning Sidebar
Description
Create new tree view in workflow extension to display remote security scan status and results.
Related Issues
Resolves #1534 (closed)
How has this been tested?
Testing with Local Scanner Service and GDK
-
Follow this to set up SAST scanner service locally using GDK
-
Check out
mainbranch on gitlab-lsp and runnpm run watch -- --editor=vscode(ref: https://gitlab.com/gitlab-org/editor-extensions/gitlab-lsp#watch-mode) -
Check out this branch and add the following to the
user settings.json(Press shift-cmd-p, type "Preferences: Open User Settings (JSON)", then press enter.)"gitlab.securityScans.enabled": true, "gitlab.featureFlags.remoteSecurityScans": true -
Follow this from step 2 to run VSCode extension locally and authenticate with your local GDK.
-
In Extension Host Extension,
-
Add this file to the test project
-
Open the test file.
-
Open workflow extension and expand Remote Scanning (SAST)
-
Hit Command+Shift+P(mac) or Ctrl + Shift + P(windows) open command palette and run
Gitlab: Run Security Scan -
Confirm scanning is in progress and items are populated when completed
-
Save the file to trigger a scan again and check if it works.
-
Testing through Staging (Unavailable until the authentication issue is resolved in staging)
-
Check out this branch and run
npm run watch -- --editor=vscode(ref: https://gitlab.com/gitlab-org/editor-extensions/gitlab-lsp#watch-mode) -
Check out
jl/1534/create-custom-scan-response-notifierbranch on gitlab-lsp -
Add to user settings.json (Press shift-cmd-p, type "Preferences: Open User Settings (JSON)", then press enter.)
"gitlab.securityScans.enabled": true, "gitlab.featureFlags.remoteSecurityScans": true -
Run vscode extension locally connected to local language server
-
In Extension Host Extension,
-
Authenticate to
staging.gitlab.comand clone an existing test project -
Add this file to the test project
-
Open the test file.
-
Open workflow extension and expand Remote Scanning (SAST)
-
Hit Command+Shift+P(mac) or Ctrl + Shift + P(windows) open command palette and run
Gitlab: Run Security Scan -
Confirm scanning is in progress and items are populated when completed
-
Save the file to trigger a scan again and check if it works.
-
Screenshots (if appropriate)
What CHANGELOG entry will this MR create?
-
fix:Bug fix fixes - a user-facing issue in production - included in changelog -
feature:New feature - a user-facing change which adds functionality - included in changelog -
BREAKING CHANGE:(fix or feature that would cause existing functionality to change) - should bump major version, mentioned in the changelog -
None - other non-user-facing changes