Commit 778be1b8 authored by Douglas Barbosa Alexandre's avatar Douglas Barbosa Alexandre

Merge branch 'enable-gpg-keys-feature-flag-by-default' into 'master'

Enable :credential_inventory_gpg_keys by default and update docs

See merge request gitlab-org/gitlab!56764
parents b566ec61 66e8012f
...@@ -56,10 +56,14 @@ The instance then notifies the user. ...@@ -56,10 +56,14 @@ The instance then notifies the user.
## Review existing GPG keys ## Review existing GPG keys
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/282429) in GitLab 13.10. > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/282429) in GitLab 13.10.
> - It's [deployed behind a feature flag](../feature_flags.md), disabled by default. > - It was [deployed behind a feature flag](../feature_flags.md), disabled by default.
> - It's disabled on GitLab.com. > - [Became enabled by default](https://gitlab.com/gitlab-org/gitlab/-/issues/292961) on GitLab 13.11.
> - It's not recommended for production use. > - It's enabled on GitLab.com.
> - To use it in GitLab self-managed instances, ask a GitLab administrator to [enable it](#enable-or-disable-the-gpg-keys-view). > - It's recommended for production use.
> - For GitLab self-managed instances, GitLab administrators can opt to [disable it](#enable-or-disable-the-gpg-keys-view).
WARNING:
This feature might not be available to you. Check the **version history** note above for details.
You can view all existing GPG in your GitLab instance by navigating to the You can view all existing GPG in your GitLab instance by navigating to the
credentials inventory GPG Keys tab, as well as the following properties: credentials inventory GPG Keys tab, as well as the following properties:
...@@ -72,10 +76,10 @@ credentials inventory GPG Keys tab, as well as the following properties: ...@@ -72,10 +76,10 @@ credentials inventory GPG Keys tab, as well as the following properties:
### Enable or disable the GPG keys view ### Enable or disable the GPG keys view
Enabling or disabling the GPG keys view is under development and not ready for production use. It is Enabling or disabling the GPG keys view 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 enable it:
......
...@@ -22,7 +22,7 @@ class Admin::CredentialsController < Admin::ApplicationController ...@@ -22,7 +22,7 @@ class Admin::CredentialsController < Admin::ApplicationController
end end
def check_gpg_keys_list_enabled! def check_gpg_keys_list_enabled!
render_404 if show_gpg_keys? && Feature.disabled?(:credential_inventory_gpg_keys) render_404 if show_gpg_keys? && Feature.disabled?(:credential_inventory_gpg_keys, default_enabled: :yaml)
end end
override :credentials_inventory_path override :credentials_inventory_path
...@@ -57,7 +57,7 @@ class Admin::CredentialsController < Admin::ApplicationController ...@@ -57,7 +57,7 @@ class Admin::CredentialsController < Admin::ApplicationController
override :gpg_keys_available? override :gpg_keys_available?
def gpg_keys_available? def gpg_keys_available?
Feature.enabled?(:credential_inventory_gpg_keys) Feature.enabled?(:credential_inventory_gpg_keys, default_enabled: :yaml)
end end
override :users override :users
......
---
title: Set credential_inventory_gpg_keys feature-flag to enabled by default
merge_request: 56764
author:
type: changed
...@@ -5,4 +5,4 @@ rollout_issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/292961 ...@@ -5,4 +5,4 @@ rollout_issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/292961
milestone: '13.8' milestone: '13.8'
type: development type: development
group: group::compliance group: group::compliance
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