►
From YouTube: GitLab 13.3 Kickoff - Release:Progressive Delivery
Description
GitLab 13.3 Kickoff - Release:Progressive Delivery
https://gitlab.com/gitlab-org/ci-cd/progressive_delivery/-/issues/6
B
A
A
We
have
done
a
big
refactor
later
in
previous
milestones,
in
order
to
make
feature
Flags
more
convenient
and
flexible
and
scalable
to
use,
and
one
of
the
problems
is
that
there
is
a
missing
feature
wherein
the
feature
flags
view.
You
cannot
see
the
environment
and
strategy
that
you
enabled
in
the
single
feature,
flan
so
I'm,
going
to
move
it
over
to
Dimitri
to
explain
a
little
bit
about
what
we
ready.
B
Yeah
thanks
so,
as
you
can
see
here
in
the
mock-ups,
we're
gonna
have
the
strategy
of
the
feature
flag
in
the
list
view
of
those
feature
Flags.
So
you
can
easily
see
how
one
will
what
is
enabled
when
a
feature
flag
is
enabled
and
in
what
way.
It's
gonna
be
added
as
a
badge
information,
UI
element
and
with
that
it's
gonna.
A
A
So
this
is
one
of
our
popular
issues
that
people
have
been
asking
for
us
to
solve,
and
the
issue
is
that
you
need
deploy
keys
for
your
project
in
order
to
work
with
the
repo
and
get
different
permissions
for
and
for
cloning
and
fetching.
And
what
happens
now
is
that
you
actually
need
to
manually
add
deploy
keys
for
every
project
within
a
group
manually
in
order
for
the
permissions
to
be
set.
So
we're
going
to
introduce
and
I'm
going
to
move
this
over
to
Dimitri
to
talk
about
the
ux
solution.
A
Great
very
excited
about
that
feature.
Our
next
topic
is
regarding
ACS,
so
new
ECS
times
definition
based
on
a
local
JSON.
We
recently
added
yet
Mopsy
Ino
template
that
allows
you
to
deploy
GCS
and
we
connected
a
DevOps
workflow.
So
now
you
have
audit
appointees.
Yes,
this
is
an
extension
on
our
current
solution,
which
allows
you
to
create
local
task
revisions
and
push
them
by
replicate
the
US
based
on
a
local
JSON
that
wasn't
previously
supported.
A
B
Thanks
much
in
terms
of
this
issue,
this
is
very
much
still
in
progress.
We're
gonna
make
it
easier
to
manage
that
gradual,
rollout
across
environments
for
a
feature
flag,
there's
various
ideas
currently
in
progress,
but
I
would
say
that
there
are
currently
toggles
and
we're
gonna
make
a
little
bit
more
flexible
to
allow
for
that
feature
flex.
He
turned
on
and
off
per
environment.
A
So
just
expand
a
little
bit
about
about
the
problem
admit
you
mentioned
this
today.
We
have
a
way
to
enable
feature
flags
for
specific
environments
to
be
toggled
on,
but
it's
a
little
bit
difficult
to
explicitly
say:
toggle
offer
specific
environments.
So
this
new
new
addition
is
going
to
make
that
much
much
easier
and
the
last
issue
that
we're
going
to
be
discussing
today
is
the
only
legacy
feature
flags,
and
this
will
actually
only
be
visible
in
the
next
milestone.
A
But
the
work
is
going
to
be
done
on
this
milestone
and
this
is
on
our
journey
from
right.
Migrating
from
v1
legacy
feature
files
into
the
new
feature,
flags
that
we
have
we
architected
slowly.
While
we
are
reaching
feature
parity
to
everything
that
we
had
in
v1,
we
are
turning.
We
will
turn
feature
Flags
the
old
feature
flags
to
read-only
in
the
UI,
so
you've
already
seen
the
banner
in
our
previous
milestones.
That
says
that
this
will
happen.
So
in
34
indeed
feature
flags
will
turn
into
read-only
in
UI.