►
Description
In this speed run, I demonstrate how to control the visibility of your container registry.
A
Okay,
so,
prior
to
this
demo,
you
can
only
control
the
container
registry
permissions
by
either
turning
the
feature
on
or
turn
it
off.
It
wasn't
possible
for
you
to
have
a
public
git
repository
with
a
private
container
registry
or
vice
versa.
We
changed
that
in
this
milestone
and
thanks
to
ruben
pereira
for
making
this
change
he's
on
the
delivery
team
at
git
lab
that
contributed.
This
feature
to
the
container
registry
awesome
job.
A
So,
let's
see
I
have.
I
have
a
test
project
here
and
if
I,
if
you
want
to
control
visibility
and
permissions,
you
go
to
the
project
settings
navigate
up
to
general.
A
A
Now
previously
the
container
registry
was
under
here
and
it
looked
just
like
this
packages
item
where
you
can
toggle
the
feature
on
and
off,
but
that
you
can't
control
permissions
at
all,
but
now
moving
forward
you
can
see.
The
container
registry
has
its
own
subheader
here
and
you
can
again,
you
can
toggle
the
feature
on
and
off
for
the
project
or
you
can
restrict
it
to
only
project
members
or
to
everyone
with
access.
A
Now,
if
you
prefer
not
to
use
the
inter
user
interface,
you
can
do
this
also
using
the
projects
api.
If
you
just
go
to
the
edit
project,
there's
a
an
item
here
for
container
registry
enabled
and
also
container
registry
access
level.
So
you
could
do
this
from
the
user
interface
or
from
using
the
api.
A
So
we
mentioned
going
back
to
my
project
that
packages
here
you
can
only
turn
the
feature
on
and
off.
Well,
I
would
just
share
this
issue
here,
where
we
that
we
currently
have
scheduled
for
14.5.
A
We
also
are
accepting
merge,
requests
in
case
you're
interested
in
contributing
this
feature
where
you
can
do
the
same
thing
where
you
could
just
like
the
container
registry,
you
can
turn
the
feature
control
it
separately
from
the
source
code.
Repository
okay.
Well,
try
it,
hopefully
that
helps
you
share
access
to
your
registry
in
a
more
secure,
efficient
manner.