代码片段群组项目

Mention Container Registry and Dependency Proxy in api scope

João Pereira 编辑于 1 year ago

The `api` scope for access tokens grants read and write access to the
Container Registry and Dependency Proxy. However, the documentation
and UI do not reflect that, they only mention the Package Registry.
This change updates the UI and documentation to reflect the current
behavior.

Changelog: changed

dd99e19d

dd99e19d 1 year ago

代码所有者

将用户和群组指定为特定文件更改的核准人。了解更多。

名称	最后提交	最后更新
..
composer_repository
conan_repository
container_registry
debian_repository
dependency_proxy
generic_packages
go_proxy
harbor_container_registry
helm_repository
maven_repository
npm_registry
nuget_repository
package_registry
pypi_repository
rubygems_registry
terraform_module_registry
workflows
yarn_repository
index.md

stage: Package
group: Package Registry
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments

Packages and Registries (FREE ALL)

The GitLab package registry acts as a private or public registry for a variety of common package managers. You can publish and share packages, which can be easily consumed as a dependency in downstream projects.

Container registry

The GitLab Container Registry is a secure and private registry for container images. It's built on open source software and completely integrated within GitLab. Use GitLab CI/CD to create and publish images. Use the GitLab API to manage the registry across groups and projects.

Terraform Module Registry

The GitLab Terraform Module Registry is a secure and private registry for Terraform modules. You can use GitLab CI/CD to create and publish modules.

Dependency Proxy

The Dependency Proxy is a local proxy for frequently-used upstream images and packages.