Skip to content

SAST Configuration UI: MVC Design

Overview

This issue defines the MVC design for the SAST Configuration UI, building off the conversations and designs in the previous UX Discovery issue.

Personas

Success Criteria

  • User can get to the SAST Configuration UI page from the Enable button on the Configuration page
  • User can configure at least some variables of the SAST template from within the UI, and create an MR to commit changes
  • User can click on View History link (if SAST is enabled) to see the git blame for the SAST .yml file

JTBD

  • When I'm enabling SAST, I want the ability to do so from within the UI so that I don't have to read a lot of documentation and go through several tedious steps to get it setup.

  • When I'm not getting the results I'd like to see from my SAST scanner, I want the ability configure the variables so that I get the most value from it and subsequently, from GitLab.

  • When something goes wrong with my SAST jobs, I want to be able to see who made changes to the SAST .yml file and when so that we can figure out how to get the jobs working properly.

Design proposal

Secure & Defend Configuration Page

Info Design
SAST not enabled. Enable button links to SAST Configuration UI page. image
SAST enabled. View history link goes to the git blame page for the SAST template. Customize button goes to the SAST Configuration UI page. image

SAST Configuration UI

Configuration UI with dynamic Restore to default link

Default (no variables changed) User changed the image prefix field (note help text below field)
image image

User clicked on View analyzers button (Analyzer section expanded)

image

Edited by Becka Lippert