Artifact Registry enables you to store different artifact types, create multiple repositories in a single project, and associate a specific region or multi-region with each repository. This page describes considerations to help you plan the locations and organization of your repositories.
Consider both internal processes for creating your artifacts and the usage by consumers of your artifacts when you create your repositories.
Each repository is associated with a specific artifact format. For example, a Python repository stores Python packages. You can create multiple repositories for each format in the same Google Cloud project.
For each repository, consider the level of access your users need. For example:
- You have a development repository for applications that are in development and production repository for applications that are released. Developers have read and write access to the development repository and read-only access to the production repository.
- You have a demo repository with sample applications. Your Sales team has read-only access to download the demos.
Labels and tags
Labels provide a way to organize resources specific to a Google Cloud service. In Artifact Registry, you can add labels to repositories so that you can group them together or filter repository lists by label. For example, you can use labels to group repositories by development stage or by team for automation or billing purposes. For more information about creating and using repository labels, see Labelling repositories.
You can also apply tags to repositories. While labels are primarily for organizing and filtering service-specific resources, tags are for programmatic control of policies across a Google Cloud organization. For more information, see Tagging repositories.
You can create multiple repositories in the same region or multi-region. A good repository location balances latency, availability, and bandwidth costs for data consumers. Your organization might also have specific compliance requirements based on the location of your data.
For information about supported locations and considerations for choosing a location, see Repository locations.