Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
d19cf6f2
Commit
d19cf6f2
authored
Nov 03, 2020
by
Krasimir Angelov
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Remove ci_secrets_management as licensed feature flag
Related to
https://gitlab.com/gitlab-org/gitlab/-/issues/273362
.
parent
5ebdd826
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
0 additions
and
8 deletions
+0
-8
config/initializers/0_inject_feature_flags.rb
config/initializers/0_inject_feature_flags.rb
+0
-1
ee/config/feature_flags/licensed/ci_secrets_management.yml
ee/config/feature_flags/licensed/ci_secrets_management.yml
+0
-7
No files found.
config/initializers/0_inject_feature_flags.rb
View file @
d19cf6f2
...
...
@@ -14,7 +14,6 @@ if Gitlab.ee? && Gitlab.dev_or_test_env?
# being unique to licensed names. These feature flags should be reworked to
# be "development" with explicit check
IGNORED_FEATURE_FLAGS
=
%i[
ci_secrets_management
feature_flags_related_issues
group_coverage_reports
group_wikis
...
...
ee/config/feature_flags/licensed/ci_secrets_management.yml
deleted
100644 → 0
View file @
5ebdd826
---
name
:
ci_secrets_management
introduced_by_url
:
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/42055
rollout_issue_url
:
group
:
group::release management
type
:
licensed
default_enabled
:
true
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment