Skip to content

Draft: Introduce new scopes for dependency proxy for containers

Radamanthus Batnag requested to merge 336800-introduce-new-dep-proxy-scopes-for-personal-access-tokens into master

What does this MR do and why?

Introduce new scopes for dependency proxy for containers

There are two current limitations with the current scopes:

  1. It uses the same scopes used by container registry, read_registry and write_registry. It is not possible to grant a user access to dependency proxy without also granting the user access to container registry.
  2. There is no read-only dependency scope. Either you can read from the dependency proxy and write to it, or you have no access to it.

This MR introduces new scopes specific to dependency proxy for containers. It does not deprecate the existing scopes; that will be done in a breaking change MR.

Changelog: added

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Related to #336800

Merge request reports