Skip to content

Pass security configuration page data to Vue

Avielle Wolfe requested to merge 13638-security-configuration-page into master

What does this MR do?

  • Adds /:namespace/:project/security/configuration route
  • Adds Projects::Security::ConfigurationController
  • Adds projects/security/configuration/show.html.haml with div#js-security-configuration
  • Adds Projects::Security::ConfigurationPresenter
  • Brings frontend variable naming related to Auto DevOps in line with backend (AutoDevOps -> AutoDevops)

The presenter contains most of the logic. It passes links to the security features' docs, a link to the project's latest pipeline, and the configuration status of each security feature to Vue as data attributes in the HAML template.

Frontend MR: !19554 (merged)
Issue: #13638 (closed)

Screenshots

An Auto DevOps pipeline reports all security jobs as configured.

Screen_Shot_2019-11-16_at_5.27.52_PM

Configuration screen built from a pipeline with all security jobs configured except container scanning.

Screen_Shot_2019-11-16_at_5.27.36_PM

A project with no default branch pipelines shows all security jobs as unconfigured.

Screen_Shot_2019-11-16_at_5.27.18_PM

Does this MR meet the acceptance criteria?

Conformity

Availability and Testing

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

  • Label as security and @ mention @gitlab-com/gl-security/appsec
  • The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
  • Security reports checked/validated by a reviewer from the AppSec team
Edited by Avielle Wolfe

Merge request reports