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
1bc5f479
Commit
1bc5f479
authored
Feb 10, 2021
by
ngaskill
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Document legacy feature flag migration
parent
3feab301
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
12 additions
and
0 deletions
+12
-0
doc/operations/feature_flags.md
doc/operations/feature_flags.md
+12
-0
No files found.
doc/operations/feature_flags.md
View file @
1bc5f479
...
...
@@ -236,6 +236,18 @@ It can be set to:
of specific users IDs to enable the feature for.
-
[
User IDs
](
#user-ids
)
## Legacy feature flag migration
Legacy feature flags became read-only in GitLab 13.4. GitLab 14.0 removes support for legacy feature
flags. You must migrate your legacy feature flags to the new version. To do so, follow these steps:
1.
Take a screenshot of the legacy flag for tracking.
1.
Delete the flag through the API or UI (you don't need to alter the code).
1.
Create a new feature flag with the same name as the legacy flag you deleted. Make sure the
strategies and environments match the deleted flag.
See
[
this video tutorial
](
https://www.youtube.com/watch?v=CAJY2IGep7Y
)
for help with this migration.
## Disable a feature flag for a specific environment
In
[
GitLab 13.0 and earlier
](
https://gitlab.com/gitlab-org/gitlab/-/issues/8621
)
,
...
...
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