►
Description
Verify the issue in https://gitlab.com/gitlab-org/gitlab/-/issues/5813
A
Hey
everyone
I'm
doing
gonna,
do
a
quick
speed
run
today
to
verify
if
a
bug
is
happening
and
if
so
share
that
in
the
issue.
So
there's
an
issue.
That's
a
bit
older
about
deploy
tokens
not
working
with
read
access
to
the
package
registry,
and
it
says
here
that
a
deploy
token
with
read
package
registry
scope
does
not
work
for
listing
the
packages
using
the
packages
api
and
there
was
a
bunch
of
discussion
down
here
that
existed,
that
we
were
talking
about.
A
A
So
we
have
this
the
packages
api,
and
with
this
you
can
list
pack
packages,
get
one
or
delete
one.
So
I'm
going
to
just
test
quickly
with
the
list
packages
group,
api,
okay,
so
and
I'll
first
test
with
a
personal
access
token,
so
I
created
well.
Let
me
start
from
scratch.
I
guess,
let's
start
with
a
group,
so
basically
I'm
going
to
copy
this
command
or
this
curl
request
and
I'm
going
to
just
put
it
into
atom.
A
Which
I've
already
done
so
there
are
a
couple
of
things
I'll
just
paste
it
in
here
for
reference
you
could
see
below.
I
had
to
put
in
the
access
token,
so
here
I'm
using
a
personal
access
token
that
I
created
and
if
you
don't
know
how
to
do
that,
you
basically
go
to
your
personal
settings
and
then
there's
a
option
here
for
access
tokens.
So
I
just
created
one
that
I
will
immediately
delete
after
this
video
and
that
will
expire
later
today.
A
The
other
information
that
you
need
to
fill
in
is
your
group
id.
This
can
be
found
within
your
group.
So
I'm
in
this
feature
testing
group
right
now,
let's
go
back
to
it
and
I
see
the
group
id
is
here
so
just
confirm:
that's
what
we
have
here:
okay,
good!
So
if
I
run
this
from
the
terminal,
it
should
re
reply
with
all
of
my
packages
for
this
group.
A
Oh,
I
should
mention
one
other
thing
and
I'd
like
to
make
a
documentation
change
is
this
option
here
is:
will
either
include
or
exclude
packages
from
subgroups?
I
believe
it
says
here
in
the
documentation
that
the
default
is.
A
Where
is
it,
the
default
is
false,
but
I
noticed
when
I
copied
this
request
and
I
could
show
you
here
again
that
it
says
true,
so
I'm
just
going
to
update
the
documentation
after
this
to
set
the
example
to
false,
since
that
is
the
default
okay.
So
I'm
going
to
copy
this
here
into
my
terminal
boom.
A
This
looks
pretty
good.
I
mean
I'm
not
going
to
check
to
see
if
every
package
is
here,
but
it
certainly
looks
like
it's
returning
a
list
of
packages.
A
A
Okay,
so
I'm
going
I'm
in
my
feature,
testing
group
and
I'm
going
to
the
settings
and
for
deploy
tokens
you
go
to
settings
repository.
I
thought
that
was
kind
of
confusing.
I
almost
was
tempted
to
look
and
see
icd
for
that,
but
here
it
is
deploy
tokens
expand
and
let's
call
this
test
packages
api
and,
let's
just
expire
it
tomorrow.
A
Choose
a
name:
okay,
it
is
optional.
I
don't
really
have
a
strong
preference
on
username
since
I'm
just
testing
this
quick.
So
let's,
for
the
sake
of
brevity,
leave
that
part
out
and
here's
the
difference
between
the
deploy
tokens
and
the
personal
access
tokens,
personal
access
tokens,
your
scopes
are
limited
to
api,
and
then
we
have
this
right,
read
registry
and
write
registry,
but
this
is
for
the
container
registry,
not
the
package
registry.
A
A
A
Unauthorized,
let's,
let's
try
one
more
time
with
a
different
scope,
so
let's
say
good:
we
got
that
collapse.
So
how
do
I
create
a
new
deploy
token.
A
A
A
A
A
Unauthorized,
so
I
think
there
there
is
indeed
a
bug
here.
It
seems
like
the
deploy
tokens
are
not
working
with
the
list
packages.
Api.