Artifact Registry creation in GCP - Mini Project: Build & Apply

Artifact Registry creation

📖 Scenario: You are setting up a secure place in Google Cloud to store your software packages. This place is called an Artifact Registry. It helps you keep your code packages safe and organized.

🎯 Goal: Create an Artifact Registry repository in Google Cloud with the right settings so you can store Docker images.

📋 What You'll Learn

Create a variable called project_id with your Google Cloud project ID as a string.

Create a variable called location with the region us-central1 as a string.

Create a dictionary called repository_config with keys repository_id set to my-docker-repo and format set to DOCKER.

Use the Google Cloud Python client library to create an Artifact Registry repository with the above settings.

Set the repository to be private by default.

💡 Why This Matters

🌍 Real World

Artifact Registry is used to store and manage software packages securely in Google Cloud. This project shows how to create a repository to hold Docker images, which is common in real-world cloud deployments.

💼 Career

Knowing how to create and manage Artifact Registry repositories is important for cloud engineers and developers working with containerized applications and CI/CD pipelines.

1

Set up project and location variables

Create a variable called project_id and set it to the string "my-gcp-project". Then create a variable called location and set it to the string "us-central1".

GCP

# Create variables project_id and location
# Your code here

Hint

Use simple assignment to create the variables with the exact strings.

2

Create repository configuration dictionary

Create a dictionary called repository_config with the keys repository_id set to "my-docker-repo" and format set to "DOCKER".

GCP

project_id = "my-gcp-project"
location = "us-central1"
# Create repository_config dictionary
# Your code here

Hint

Use curly braces to create the dictionary with the exact keys and values.

3

Import client and prepare repository creation

Import ArtifactRegistryClient from google.cloud.artifactregistry_v1. Then create a client instance called client. Use the repository_config dictionary to prepare a repository creation request with the repository ID and format.

GCP

project_id = "my-gcp-project"
location = "us-central1"
repository_config = {
    "repository_id": "my-docker-repo",
    "format": "DOCKER"
}
# Import ArtifactRegistryClient and create client instance
# Your code here

Hint

Use the import statement exactly as shown and create the client instance with no arguments.

4

Create the Artifact Registry repository

Use the client to call create_repository with the parent path built from project_id and location. Pass a repository object with name set to the full repository path, format from repository_config, and description set to "Docker repository". This will create a private Docker repository.

GCP

from google.cloud.artifactregistry_v1 import ArtifactRegistryClient

project_id = "my-gcp-project"
location = "us-central1"
repository_config = {
    "repository_id": "my-docker-repo",
    "format": "DOCKER"
}

client = ArtifactRegistryClient()
# Create the repository using client.create_repository
# Your code here

Hint

Use the full parent path and repository name. Call operation.result() to wait for creation.

Practice

1. What is the main purpose of creating an Artifact Registry in Google Cloud?

easy

A. To host virtual machines

B. To securely store and manage software packages

C. To monitor network traffic

D. To create databases

Solution

1. Step 1: Understand Artifact Registry purpose

   Artifact Registry is designed to store and manage software packages securely.

2. Step 2: Compare options with purpose

   Options B, C, and D relate to other services like Compute Engine, VPC, and Cloud SQL, not Artifact Registry.

3. Final Answer:

   To securely store and manage software packages -> Option B

4. Quick Check:

   Artifact Registry = Secure package storage [OK]

Hint: Artifact Registry = package storage, not VMs or databases [OK]

Common Mistakes:

• Confusing Artifact Registry with Compute Engine
• Thinking it manages databases
• Assuming it monitors network traffic

2. Which of the following is the correct command syntax to create an Artifact Registry repository with Docker format in region us-central1?

easy

A. gcloud artifacts repositories create my-repo --repository-format=docker --location=us-central1

B. gcloud artifacts create repository my-repo --format=docker --region=us-central1

C. gcloud create artifacts repository my-repo --format=docker --location=us-central1

D. gcloud artifacts repositories new my-repo --repository-format=docker --location=us-central1

Solution

1. Step 1: Recall correct gcloud command structure

   The correct command is 'gcloud artifacts repositories create' followed by repository name and flags '--repository-format' and '--location'.

2. Step 2: Match options with correct syntax

   gcloud artifacts repositories create my-repo --repository-format=docker --location=us-central1 matches the correct syntax exactly. Other options have wrong order or wrong flags.

3. Final Answer:

   gcloud artifacts repositories create my-repo --repository-format=docker --location=us-central1 -> Option A

4. Quick Check:

   Correct command syntax = gcloud artifacts repositories create my-repo --repository-format=docker --location=us-central1 [OK]

Hint: Use 'gcloud artifacts repositories create' with format and location [OK]

Common Mistakes:

• Using 'create' before 'artifacts repositories'
• Mixing up --region and --location flags
• Incorrect flag names like --format instead of --repository-format

3. What will be the result of running this command?

gcloud artifacts repositories create test-repo --repository-format=maven --location=us-east1

medium

A. Creates a Docker format repository ignoring the format flag

B. Fails because 'maven' is not a valid repository format

C. Creates a Maven format Artifact Registry repository in us-east1 region

D. Creates a repository but defaults location to global

Solution

1. Step 1: Check repository format validity

   'maven' is a valid repository format supported by Artifact Registry.

2. Step 2: Check location flag effect

   Specifying '--location=us-east1' sets the repository region correctly.

3. Final Answer:

   Creates a Maven format Artifact Registry repository in us-east1 region -> Option C

4. Quick Check:

   Valid format and location = Creates a Maven format Artifact Registry repository in us-east1 region [OK]

Hint: Supported formats include maven, docker, npm, etc. [OK]

Common Mistakes:

• Assuming 'maven' is invalid format
• Thinking location defaults to global if specified
• Believing format flag is ignored

4. You run this command but get an error:

gcloud artifacts repositories create my-repo --repository-format=pip --location=us-west1

What is the likely cause?

medium

A. Missing project flag in the command

B. The location 'us-west1' is invalid

C. Repository name 'my-repo' is invalid

D. The repository format 'pip' is not supported

Solution

1. Step 1: Verify supported repository formats

   Artifact Registry does not support 'pip' as a repository format; common formats are docker, maven, npm, etc.

2. Step 2: Check location and name validity

   'us-west1' is a valid location and 'my-repo' is a valid name; missing project flag usually defaults to current project.

3. Final Answer:

   The repository format 'pip' is not supported -> Option D

4. Quick Check:

   Unsupported format causes error = The repository format 'pip' is not supported [OK]

Hint: Check format spelling and support before creating repo [OK]

Common Mistakes:

• Assuming all language names are valid formats
• Ignoring error messages about format
• Thinking location or name is the problem

5. You want to create an Artifact Registry repository that supports both Docker and npm packages in the us-central1 region. What is the best approach?

hard

A. Create two separate repositories: one with format docker and one with format npm, both in us-central1

B. Create one repository with format docker,npm in us-central1

C. Create a repository with format docker and upload npm packages to it

D. Create a repository with format npm and upload docker images to it

Solution

1. Step 1: Understand repository format limitation

   Artifact Registry repositories support only one format each; you cannot mix formats in one repository.

2. Step 2: Plan repository creation accordingly

   To support both Docker and npm, create two repositories with respective formats in the same region.

3. Final Answer:

   Create two separate repositories: one with format docker and one with format npm, both in us-central1 -> Option A

4. Quick Check:

   One format per repo = Create two separate repositories: one with format docker and one with format npm, both in us-central1 [OK]

Hint: One repo = one format; use multiple repos for multiple formats [OK]

Common Mistakes:

• Trying to combine formats in one repository
• Uploading wrong package types to a repo
• Ignoring regional consistency