►
From YouTube: GitLab 12.10 Kickoff - Package:Package
Description
Details about features being planned for GitLab 12.10 for the Package stage
A
Okay,
let's
go
through
some
of
the
features.
The
first
one
I
wanted
to
talk
about
was
a
an
expanded
scope
for
the
gate,
lab
deploy
tokens
for
the
packaging
container
registries.
So
as
of
right
now,
the
deploy
tokens
only
cover
or
will
only
allow
you
to
read
the
repository
and
read
from
the
container
registry.
It
doesn't
support
the
package
registry
and
it
doesn't
support,
write
access
as
well.
A
A
The
next
feature
I
wanted
to
talk
about
we're
prioritizing
the
work
in
12.10.
It
is
possible.
This
will
select
two
milestones,
13-point
o-o,
which
is
will
be
due
out
in
June
2020,
but
the
proposed
MVC
scope
for
this
is
that
you
can
add,
get
lab
as
a
remote
repository
for
your
PI
pi
projects,
you'll
be
able
to
authenticate
using
your
username
and
password,
or
your
get
lab
personal
access.
A
A
The
next
one
I
wanted
to
talk
about
is
a
is
I'm
really
excited
about
is
for
the
--get
lab
dependency
proxy,
allowing
you
to
de
purge
any
items
from
the
cache.
So
basically,
this
is
an
API
which
will
allow
you
to
purge
the
entire
cash
for
the
dependency
proxy
and
then
in
the
future.
What
will
do
is
will
actually
allow
you
to
define
the
cadence
of
this
as
part
of
the
API
and
then
we'll
add
in
a
user
interface
that
will
allow
you
to
schedule
it
and
purge
the
cache
from
the
user
interface.
A
A
lot
of
our
system
administrators
out
there
in
the
community
reached
out
to
me
and
said
they
really
want
to
be
able
to
expand
this
to
existing
projects,
and
they
want
to
be
able
to
configure
this
application
setting
on
their
own
and
and
not
have
us
dictate
that
only
new
projects
12-8
forward
should
be
enabled.
So
what
we're
doing
is
we
will
add
a
column
to
the
application
settings
that
will
allow
you
to
determine
if
you
want
the
expiration
policies
to
be
turned
on
only
for
new
projects
forward
or
for
all
historical
projects
as
well.
A
Ok
see
what
else.
There
are
also
a
bunch
of
user
interface
improvements
that
we're
making
for
for
this
round.
So
we
will
always
show
copyable
til
the
the
copyable
build
and
push
commands
for
the
container
registry.
Currently
right
now,
basically
it'll.
We
only
show
this
screen
when
you
don't
have.
Any
images
in
the
registry
will
basically
be
moving
this
to
a
button
that
persists.
Even
once
you
have
items
in
the
registry,
you'll
be
able
to
click
setup
and
you'll
be
able
to
copy
the
initial
setup
commands
that
were
there.
A
We
are
updating
the
package
registry
user
interface
in
a
bunch
of
ways,
we're
adding
more
robust
data
into
the
title
section
of
the
UI
and
to
the
ListView
as
well,
and
we're
also
adding
the
ability
to
filter,
by
name
in
the
package
list.
So
now
you
can
quickly
just
type
in
the
name
of
the
package,
you're
looking
for
and
be
able
to
filter
the
options
quickly
for
it.