Artifact Registry creation in GCP - Step-by-Step Execution

Process Flow - Artifact Repository creation

Start

↓

Define Repository Config

↓

Send Create Request

↓

Wait for Confirmation

↓

Repository Created

↓

Use Repository for Storing Artifacts

The flow shows defining the repository, sending the creation request, waiting for confirmation, and then using the repository.

Execution Sample

GCP

gcloud artifacts repositories create my-repo \
  --repository-format=docker \
  --location=us-central1 \
  --description="My Docker repo"

This command creates a Docker format repository named 'my-repo' in Artifact Registry in the 'us-central1' region.

Process Table

Step	Action	Input/Config	Result	Notes
1	Define repository name and format	Name: my-repo, Format: docker	Config ready	Prepare parameters for creation
2	Specify location	Location: us-central1	Location set	Region chosen for repository
3	Send create request	gcloud artifacts repositories create ...	Request sent	API call initiated
4	Wait for confirmation	Waiting...	Repository created	Repository is now available
5	Verify repository	gcloud artifacts repositories list	my-repo listed	Confirm repository exists
6	Use repository	Push/pull artifacts	Artifacts stored/retrieved	Repository operational

💡 Repository creation confirmed and ready for use

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
repository_name	undefined	my-repo	my-repo	my-repo	my-repo	my-repo
repository_format	undefined	docker	docker	docker	docker	docker
location	undefined	undefined	us-central1	us-central1	us-central1	us-central1
creation_status	not started	not started	not started	request sent	created	created

Key Moments - 3 Insights

Why do we need to specify the location before creating the repository?

The location determines where your repository data is stored physically. In the execution_table step 2, setting location ensures the repository is created in the desired region.

What happens if the create request fails?

If the request fails, the creation_status variable in variable_tracker would not change to 'created' as shown in step 4. You would need to check error messages and retry.

Can we use the repository immediately after sending the create request?

No, as shown in step 4, you must wait for confirmation that the repository is created before using it. Trying to use it too early will cause errors.

Visual Quiz - 3 Questions

Look at the variable_tracker table, what is the value of 'creation_status' after step 3?

A not started

B created

C request sent

D failed

💡 Hint

Check the 'creation_status' row under 'After Step 3' column in variable_tracker.

At which step in the execution_table does the repository become available for use?

A Step 3

B Step 4

C Step 5

D Step 6

💡 Hint

Look for the step where 'Repository created' is the result in execution_table.

If the location was not specified, how would the execution_table change?

A Step 3 would fail due to missing location

B Step 2 would show 'Location set' as usual

C Step 4 would confirm creation anyway

D Step 5 would list the repository with default location

💡 Hint

Consider the importance of location in step 2 and its effect on the create request in step 3.

Concept Snapshot

Artifact Repository creation:
- Use 'gcloud artifacts repositories create' command
- Specify repository name, format (e.g., docker), and location
- Wait for creation confirmation before use
- Verify with 'gcloud artifacts repositories list'
- Use repository to store and retrieve artifacts

Full Transcript

To create an Artifact Registry repository in Google Cloud, first define the repository name and format, such as 'my-repo' and 'docker'. Then specify the location where the repository will be stored, for example 'us-central1'. Next, send the create request using the gcloud command. Wait for confirmation that the repository is created. Once confirmed, verify the repository exists by listing repositories. Finally, use the repository to push and pull artifacts. The process ensures the repository is properly configured and ready for use.

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