Skip to content

Security Configuration enablement is confusing for users, does not indicate the need for a successful generation of an artefact to show as enabled.

Per this conversation on Slack.

When enabling scanners for a project, an MR is generated to enable the respective scanner in the .gitlab-ci.yml configuration, but it's not indicated to the user that in order for the scanner configuration to be recognised as enabled, the pipeline needs to run and successfully generate a respective artefact. This can leave the user feeling confused as to why the feature isn't being enabled correctly.

image

Possible Solutions

  • Indicate to the user that the configuration will not reflect as enabled until the pipeline has been successfully executed and generated valid artefacts.
  • Create a troubleshooting section in the documentation, and add an explicit Troubleshooting link to the Security Scanners configuration page.