Configure Container Registry access/visibility level
Summary
Container registry access should be configurable like all other project level features
Original description:
Hi, trying to access our registry at https://gitlab.com/gitmate/open-source/gitmate-2/container_registry always yields a 502. What's going on there?
Also I haven't found a way to keep the registry private for a public repo.
Steps to reproduce
- Create a new project
- Navigate to the Project's settings
- Navigate to the Permissions settings
What is the current bug behavior?
Container registry feature can only be disabled and reenabled
What is the expected correct behavior?
Enable access to the Container Registry for a project to be restricted:
- Everyone with access
- Team members only
- Disabled
Output of checks
(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)
Results of GitLab environment info
reproduced on GitLab.com v10.0.0-rc5
Results of GitLab application Check
reproduced on GitLab.com v10.0.0-rc5
Possible fixes
Edited by Mark Fletcher