►
From YouTube: GitLab 13 4 Kickoff - Configure:Configure
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello,
my
name
is
victor
knight,
I'm
the
product
manager
of
the
configure
group,
and
this
is
the
risk
of
video
of
our
group.
Following
my
recording,
you
will
hear
the
parts
presented
by
my
ux
counterpoint,
monitor
ratchet
that
are
related
to
the
design
and
ux
work.
We
plan
for
for
this
milestone
and
I'm
going
to
focus
only
on
the
development
work
that
we
want
to
ship,
or
at
least
want
to
start
to
work
on.
A
A
A
A
A
A
A
A
The
final
item
I
want
to
speak
about
this
related
to
commander's
management
in
this
release,
is
the
ability
to
customize
commander's,
name
spaces
per
environment.
In
the
case
of
gitlab
managed
clusters
for
non-gitlab
managed
casters,
you
could
customize
namespace
for
a
long
time,
but
gitlamesh
clusters
had
this
shortcoming
and
actually,
until
a
few
months
ago,
we
had
an
approach
where
we
had
one
namespace
per
project.
A
We
have
changed
this
to
have
one
namespace
per
environment.
Thus
every
review
app
has
its
own
namespace
and
a
few
of
our
users
are
not
happy
with
this
change
and
prefer
the
previous
method.
Actually,
so,
as
we
are
supporting
it,
we
are
just
allowing
them
in
the
future
to
have
a
selection,
which
is
their
preferred
method
and
we
can
support
both
setups.
At
the
same
time,
this
was
proposed
by
one
of
our
users
who
favors
the
word
method,
and
it's
pretty
minor
undertaking
that
we
think
will
benefit
quite
a
few
of
our.
A
Users,
why
might
I
show
you
a
get
github
page
on
a
release?
Kickoff
video
for
a
very
simple
reason,
hashicorp
reached
out
to
us
a
month
ago
that,
with
the
release
of
terraform
13.0,
they
are
moving
out.
Trafform
managed
providers
to
their
to
their,
let's
see,
meaning
for
logical
owner
places,
and
they
would
like
us
to
take
over
the
gitlab
terraform
provider.
A
A
We
still
have
a
lot
of
work
to
do
to
do
around
taking
over
the
provider,
and
we
want
to
finish
these
tasks
in
the
coming
milestone.
At
the
same
time,
we
are
figuring
out
the
flows
and
the
communication
channels
around
developing
the
provider
itself,
because
the
configure
team
can't
take
all
the
gitlab
side,
developments
that
are
requested
by
our
users
to
add
support
to
various
parts
of
the
tranform
provider.
A
This
is
actually
the
issue
that
we
are
focusing
on,
where
we
try
to
collect
the
most
sensitive
traffic
provider
related
developments,
and
we
are
usually
just
pinging
the
group
who
is
actually
responsible
for
giving
part
for
reviewing
changes
or
for
coming
up
with
fixes
around
needed
developments.
Here.
A
B
B
B
B
This
issue
has
to
do
with
the
information
regarding
the
infrastructure
changes,
so
the
stage
file
changes
in
bmr,
which
is
currently
designed
to
in
the
mr
widget
in
the
mr
page.
So
the
scope
of
this
issue
is
to
create
a
more
scalable
design
that
will
allow
us
to
enhance
the
experience
and
information
we
provide
to
the
users
around
state
files,
such
as
support,
multiple
state
files
or
show
more
specific
information
regarding
the
infrastructure
changes
through
this
through
a
specific.
Mr.