►
From YouTube: GitLab 15.6 Kickoff - Enablement:Distribution
Description
Planning Issue - https://gitlab.com/gitlab-org/distribution/team-tasks/-/issues/1131
A
A
If
you
will
so,
we've
been
working
on
many
urgent
crosstourial
cross
portfolio
projects
and
compliance
work
for
the
past
few
Milestones,
and
this
is
an
opportunity
for
us
to
catch
up
quote
unquote
with
some
of
the
work
that
had
to
be
pushed
out
due
to
those
you
know
highly
urgent
issues.
So
the
main
bulk
of
the
work
is
going
to
be
sort
of
miscellaneous
and
not
a
general
theme,
but
if
you're
interested
in
viewing
all
the
items
again,
you
can
view
the
deliverable
board
here.
A
I'll
talk
about
a
couple
of
them
and
then
another
one
that
you
know.
One
of
the
big
things
that
we're
working
on
is
the
secure
solution
for
managing
Omnibus
Secrets.
This
is
one
I've
talked
about
for
a
while.
If
you've
been
watching
these
videos
and
then
finally
getting
around
to
it,
it's
an
important
issue.
So
it's
good
we're,
finally
tackling
it.
So
moving
to
the
first
issue
here,
we've
got
added
packages
for
Amazon
Linux
2022.,
so
this
is
pretty
exciting.
A
A
So
this
relates
to
an
issue
that
we're
currently
working
on
that
I
believe
I
mentioned
in
the
last
video,
which
is
you
know,
supporting
Cloud
native
gitlab
installation
on
arm64
architecture.
This
is
sort
of
the
next
phase
of
that
so
very
excited
about
enabling
this
work
for
folks
who
want
to
run
on
arm
64
architecture.
A
Now
moving
on,
we've
got
two
sub
issues
for
the
Secure
Solutions
for
managing
Omnibus
Secrets,
epic,
the
first
one
is
encrypting
all
passwords,
all
rails,
passwords,
sorting,
gitlab.rb
and
the
next
one
is
all
non-rails
passwords.
So
you
can
see,
we've
got
a
list
of
the
passwords
here
for
rails,
passwords
and
we've
got
a
list
of
the
issues
or
excuse
any
passwords
here
for
non-rails
passwords,
so
we're
going
to
slowly
chunk
through
these
I
believe
we've
got
a
handful
of
these
scheduled
and
then
this
one
is
more
of
a
spike.
A
We
did
did
a
spike
a
few
months
ago,
but
we
kind
of
reached
the
stopping
point.
So
we
want
to
Circle
back
to
this
one
and
kind
of
finish
out
how
this
could
be
feasible,
so
you
can
start
again
making
progress
on
these.
So
these
all
Loop
into
again
this
issue
for
secure
solution
for
managing
Omnibus
configuration
secrets.
So
right
now
these
configuration
files
contain
plain
text
passwords
and
we've
been
notified.
This
is
not
a
a
good
security
practice
for
some
of
the
organizations
that
we
work
with.
A
So
obviously
we
want
to
mitigate
that
as
soon
as
possible,
so
yeah.
That
is
basically
rounding
out
a
couple
of
the
Highlight
issues
that
I
want
to
talk
about.
We
have
a
full
Board
of
issues
again
that
we're
going
to
be
working
on
I.
Just
don't
want
to
you
know,
mention
all
the
issues
they're
all
important.
Some
of
them
are
maintenance
work
on
our
end
and
yeah,
so
feel
free
to
take
a
look
at
our
delivery
board.