►
Description
Speedrun of a new feature available in 14.2. You can now authenticate using a group deploy token when pulling images using the dependency proxy.
A
Hello,
I'm
tim,
I'm
the
pm
for
the
package
stage,
and
today
I
was
hoping
to
do
a
quick
speed
run
of
a
feature
for
the
dependency
proxy,
that's
available
now
on
gitlab.com
and
will
be
included
in
the
14.2
release.
So
right
now
you
can
use
the
dependency
proxy
to
proxy
and
cache
images
from
docker
hub
to
help
you
reduce
your
reliance
on
external
dependencies.
A
You
can
avoid
docker
hub
rate
limits
and
also
speed
up
your
builds
prior
to
this
issue
being
completed.
You
can
authenticate
using
some
predefined
environment
variables
that
we
have
or
a
personal
access
token,
but
having
talked
to
many
of
you
in
the
community
and
our
customers,
we
heard
that
it's
really
important
to
be
able
to
use
deploy
tokens
for
this
for
this
feature
as
well.
A
A
Okay.
So
let's
see
let's
break
that
down
into
pieces.
The
first
step
is
going
to
be
to
create
the
deploy
token.
So
for
that,
what
I
actually
did
was
go
into
my
subgroup,
I'm
going
to
open
that
in
another
tab-
and
this
just
has
a
few
projects
in
here
for
the
dependency
proxy
that
I
work
have
worked
on.
And
then,
if
I
go
to
settings
and
to
repository.
A
I
can
see
here
that
the
option
to
create
deploy
tokens-
I
can
expand
this
and
once
you're
here
you
can
name
it
whatever
you
want,
you
can
assign
an
expiration
date.
You
can
enter
a
username
if
you
wanted
to,
but
for
the
dependency
proxy.
What's
important
is
that
you
give
access
to
both
read
and
write
registry
once
you
do
that,
once
you
hit
submit,
it
will
create
a
token
and
it'll
populate
values
here
and
then
what
I
did
after
that
was
go
and
create
some
project.
A
A
A
Well,
if
I
go
back
to
that
group,
so
here
I'm
in
that
I'll
just
open
it,
so
you
can
see
my
sub
subgroup
here
and
if
I
navigate
to
just
expand
it
to
packages
and
registries,
I
could
see
the
dependency
proxy,
and
here
I
could
see
the
dependency
proxy
url.
Now
one
important
thing
and
actually
a
fix,
that's
coming
out
of
this
demo.
Is
you
don't
want
to
include
the
https
here?
A
A
A
Okay
yeah,
so
it
finished,
and
I
could
see
here
that
docker
login
was
successful
and
then
I
could
see
that
the
my
latest
nginx
image
was
pulled
properly,
so
yeah
I
was
able
to
just
using
a
group,
deploy
token
proxy
and
cache
an
image
using
a
without
a
problem
using
gitlab
ci
and
if
you
have
any
questions,
feel
free
to
add
a
comment
to
the
issue
and
let
us
know
how
you're
enjoying
the
feature.
Thank
you.
Everyone.