Add Auto DevOps alert to Security Configuration page
requested to merge 220573-frontend-modify-secure-configuration-page-to-provide-entry-point-to-sast-config-ui-page into master
What does this MR do?
This is adds the Auto DevOps alert as described in #220573 (closed).
This alert is displayed only when all the following is true:
- A project has no existing
.gitlab-ci.yml
file - Auto DevOps is not enabled for the project
- The user has the necessary permissions to enable Auto DevOps for the project
- The
sast_configuration_by_click
feature flag is enabled (it's currently disabled by default)
Note
While this frontend work depends on the backend work being done, because this is behind a feature flag, it should be safe to merge in any order.
Testing locally
- Merge (or cherry-pick) the backend work done in !36225 (merged) into this branch locally
- Enable the
sast_configuration_by_click
feature flag - Navigate to or set up a project that satisfies the above requirements
Screenshots
Before | After (i.e., no change) | After + feature flag enabled |
---|---|---|
Does this MR meet the acceptance criteria?
Conformity
- [-] Changelog entry
- [-] Documentation (if required)
-
Code review guidelines - [-] Merge request performance guidelines
-
Style guides - [-] Database guides
-
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. - [-] Tested in all supported browsers
- [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Edited by Mark Florian