SAST Config UI - Analyzers
SAST Config UI - Analyzers
Problem to Solve
Provide UI to easily configure SAST analyzers
Note: Button labels should be Expand
and Collapse
Collapsed analyzer section (Default)
Expand
button)
Expanded analyzer section (user clicked
Unchecked analyzer ("off" state)
See Flawfinder example below where text input is disabled
Implementation Strategy
frontend (this is perhaps best done after gitlab#227575 (closed), otherwise more would have to ported to GQL later)
-
frontend-weight2 Create expandable container component (likely under
ee/app/assets/javascripts/security_configuration/sast/components
)- See internal discussion on this.
-
frontend-weight2 Create
AnalyzersConfiguration
component- Uses the expand/collapse component
- Receives
analyzers
configuration from GQL query as a prop - emits an
input
event with updated deep copy ofanalyzers
prop, with changes applied
-
frontend-weight3 Consume
AnalyzersConfiguration
component inConfigurationForm
- Update
ConfigurationForm
to receive the analyzers configurations in addition to global + pipeline entities. Perhaps just the whole GQL response as-is? Perhaps renameentities
prop tosastCiConfiguration
, orconfiguration
? - emits new copy of above prop with changes included
- Update form submission logic to structure expected by backend (TBD)
- Update
-
backend-weight3 Read SAST template file and
.gitlab-ci.yml
files to decide whether analyzer is enabled. This issue will address this work. -
backend-weight3 Read SAST template file and
.gitlab-ci.yml
files to get information about different variables at analyzer level. This issue will address this work. -
backend-weight3 Store the information about analyzers in
.gitlab-ci.yml
file issue
TBC @ssarka @rossfuhrman
Relevant links:
- 13.5 release post - analyzers & existing config parsing
Release notes
Release post items have been generated: gitlab-com/www-gitlab-com!64767 (merged)
- Show closed items
Link items together to show that they're related or that one is blocking others.