FE: Link to SAST Config UI in projects with CI file
The Security Configuration page currently only links to the SAST Configuration page for projects without an existing CI file. This is because the initial implementation did not support updating an existing CI file.
With #232862 (closed) addressed, that technical limitation has been lifted (with caveats, e.g., #228959 (closed)).
This issue tracks the frontend changes needed to make the Security Configuration page link to the SAST Configuration page for projects with an existing CI file.
Questions
- Should this change be behind a feature flag?
Implementation plan
- [-] Remove
gitlab_ci_present
value passed from controller - [-] Remove branches relying on
gitabCiPresent
from frontend
Actually, it turned out gitlab_ci_present
is used elsewhere, so had to be kept.
Edited by Mark Florian