►
A
So
I'm
going
to
go
ahead
and
share
my
screen
and
walk
you
through
the
process
so
feature
flags
are
located
under
your
project
under
operations,
feature
flags
and
if
you
already
are
using
legacy
feature
flags,
you
may
have
noticed
this
new
tooltip.
That
shows
you
on
legacy
flags
that
flag
becomes
read
only
soon
and
if
you
attempted
to
edit
the
flag
you
may
have
seen
this
note.
That
said,
gitlab
is
moving
to
a
new
way
of
managing
future
flags
and
in
13.4,
which
is
the
next
milestone.
A
This
feature
flag
will
become
read.
Only
please
create
a
new
feature
flag.
So
the
good
news
about
the
migration
is
that
there's
no
need
to
change
anything
in
the
code.
You
just
need
to
change
the
feature
flag
in
gitlab,
so
you
can
do
this
through
ui
or
through
api.
I'm
going
to
demonstrate
how
to
do
it
in
ui,
for
this
speed
run.
A
What
we
need
to
do
is
we
need
to
create
a
new
flag
that
basically
is
going
to
have
the
same
name
as
the
previous
flag,
and
then
everything
is
just
going
to
work.
So
let's
go
ahead
and
do
that
together.
The
the
bad
news
is
that
you
can't
edit
the
legacy
flags,
so
you
can't
you
know
rename
this
to
like
demos
underscore
old
and
then
just
replace
it
easily.
We're
gonna
have
to
do
it
in
the
next
phases.
We
need
to
create
a
new
flag
with
a
new
name.
A
We
need
to
delete
the
old
flag
and
then
create
a
new
flag
with
the
previous
name.
We
can
also,
alternatively,
alternatively,
just
delete
the
old
flag
and
create
a
new
flag
under
the
new
name.
A
A
So
I
have
this
old
flag
called
demo
and
what
I
want
to
do
is
I
want
to
create
a
new
flag,
I'm
going
to
call
this
demo
underscore
new
and
I'm
going
to
try
to
copy
all
the
metadata
from
the
old
flag
to
the
new
flag.
So
I
have
the
name
which
I'm
going
to
need
to
change
after
creating
this
flag,
I'm
going
to
create
copy
the
description
and
then
I'm
going
to
copy
the
environment
specs.
A
A
A
Okay-
and
I
even
have
another
strategy
here-
for
specific
user
ids
in.
A
A
And
you
can
see
that
I
have
my
demo
new.
It
has
all
users
for
all
environments,
then
I
have
percent
usage
users
50
on
testing
15
on
production.
The
previous
legacy
didn't
show
me
that
this
was
also
enabled
for
user
id.
So
you
can
see
we
even
have
an
enhancement
here
in
the
new
feature
flags,
where
you
can
also
see
the
specific
user's
ids
that
are
enabled,
for
course,
for
a
specific
environment.
So
we
have
four
users
and
testing
four
users
in
production.
A
So
now
that
I'm
happy
with
my
new
flag,
I
can
also
make
sure
that
the
toggle
is
the
same
state
so
that
it
is
exactly
the
same.
So
at
this
moment
this
specific
feature
flag
is
created,
but
it's
not
connected
to
the
code,
because
the
flag
name
doesn't
match
what
is
written
in
the
code.
So
we're
going
to
go
ahead
and
delete
our
old
feature,
flag
demo.
A
It
was
deleted
and
now
I'm
going
to
go
ahead
and
edit
my
new
flag,
so
that
it
has
the
old
name
demo
and
that's
it
from
this
moment
on
it
reflects
what
was
configured
in
the
code,
and
this
is
our
new
flag.
There
is
no
need
again
to
change
anything
in
the
code,
so
now,
if
I
turn
it
on,
it
will
work.
I
turn
it
off.
It
will
be
disabled.
A
So
I
want
to
thank
you
for
your
time
for
watching
this
video
today.
I
hope
this
helps.
You
understand
the
migration
path
for
the
new
feature,
flags
and
I'll,
see
you
next
time
in
our
next
speed
run.
Thank
you.