Enable sec_dependency_scanning_ui_enable by default

This enables the sec_dependency_scanning_ui_enable feature flag by
default, making the "Configure via Merge Request" button publicly
available for Dependency Scanning.

Changelog: added
EE: true
parent 92964136
...@@ -112,16 +112,20 @@ always take the latest dependency scanning artifact available. ...@@ -112,16 +112,20 @@ always take the latest dependency scanning artifact available.
### Enable Dependency Scanning via an automatic merge request ### Enable Dependency Scanning via an automatic merge request
> - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/4908) in GitLab 13.11. > - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/4908) in GitLab 14.1.
> - [Deployed behind a feature flag](../../../user/feature_flags.md), disabled by default. > - [Deployed behind a feature flag](../../../user/feature_flags.md), enabled by default.
> - Disabled on GitLab.com. > - Enabled on GitLab.com.
> - Not recommended for production use. > - Recommended for production use.
> - To use in GitLab self-managed instances, ask a GitLab administrator to [enable it](#enable-or-disable-configure-dependency-scanning-via-a-merge-request). > - For GitLab self-managed instances, GitLab administrators can opt to [disable it](#enable-or-disable-configure-dependency-scanning-via-a-merge-request). **(ULTIMATE SELF)**
WARNING: WARNING:
This feature might not be available to you. Check the **version history** note above for details. This feature might not be available to you. Check the **version history** note above for details.
If Dependency Scanning isn't yet enabled in your project, you can automatically create a merge request There can be
[risks when disabling released features](../../../user/feature_flags.md#risks-when-disabling-released-features).
Refer to this feature's version history for more details.
To enable Dependency Scanning in a project, you can create a merge request
from the Security Configuration page. from the Security Configuration page.
1. In the project where you want to enable Dependency Scanning, navigate to 1. In the project where you want to enable Dependency Scanning, navigate to
...@@ -680,19 +684,19 @@ For information on this, see the [GitLab Secure troubleshooting section](../inde ...@@ -680,19 +684,19 @@ For information on this, see the [GitLab Secure troubleshooting section](../inde
### Enable or disable Configure Dependency Scanning via a Merge Request ### Enable or disable Configure Dependency Scanning via a Merge Request
Configure Dependency Scanning via a Merge Request is under development and not ready for production use. It is Configure Dependency Scanning via a Merge Request is under development but ready for production use.
deployed behind a feature flag that is **disabled by default**. It is deployed behind a feature flag that is **enabled by default**.
[GitLab administrators with access to the GitLab Rails console](../../../administration/feature_flags.md) [GitLab administrators with access to the GitLab Rails console](../../../administration/feature_flags.md)
can enable it. can opt to disable it.
To enable it: To disable it:
```ruby ```ruby
Feature.enable(:sec_dependency_scanning_ui_enable) Feature.disable(:sec_dependency_scanning_ui_enable)
``` ```
To disable it: To enable it:
```ruby ```ruby
Feature.disable(:sec_dependency_scanning_ui_enable) Feature.enable(:sec_dependency_scanning_ui_enable)
``` ```
...@@ -5,4 +5,4 @@ rollout_issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/326005 ...@@ -5,4 +5,4 @@ rollout_issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/326005
milestone: '13.11' milestone: '13.11'
type: development type: development
group: group::composition analysis group: group::composition analysis
default_enabled: false default_enabled: true
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment