Project configuration in GCP - Commands & Configuration

Introduction

Setting up a project in Google Cloud Platform helps organize your resources and control access. It solves the problem of managing multiple cloud resources under one roof with clear billing and permissions.

When you want to keep your app resources separate from other projects for better management.

When you need to assign specific permissions to team members for only certain resources.

When you want to track costs and billing for a specific app or environment.

When you plan to enable APIs and services only for a particular project.

When you want to isolate development, testing, and production environments.

Commands

This command creates a new Google Cloud project named 'Example Project' with the ID 'example-project-12345' and sets it as the default project for future commands.

Terminal

gcloud projects create example-project-12345 --name="Example Project" --set-as-default

Expected Output

Created project [example-project-12345].

→

--name - Sets the display name of the project.

→

--set-as-default - Makes this project the default for gcloud commands.

This command explicitly sets the active project to 'example-project-12345' for all subsequent gcloud commands.

Terminal

gcloud config set project example-project-12345

Expected Output

Updated property [core/project].

This command shows details about the project, such as its name, project ID, number, and lifecycle state, confirming the project exists and is configured.

Terminal

gcloud projects describe example-project-12345

Expected Output

createTime: '2024-06-01T12:00:00.000Z'

lifecycleState: ACTIVE

name: Example Project

projectId: example-project-12345

projectNumber: '123456789012'

This command enables the Compute Engine API for the current project, allowing you to create and manage virtual machines.

Terminal

gcloud services enable compute.googleapis.com

Expected Output

Operation "operations/enable-compute.googleapis.com" finished successfully.

Key Concept

If you remember nothing else, remember: a GCP project is the main container for your cloud resources and controls access and billing.

Common Mistakes

Trying to create a project with an ID that is already taken.

Project IDs must be unique across all Google Cloud users, so duplicates are not allowed.

Choose a unique project ID by adding numbers or your organization name.

Not setting the project as default after creation.

Without setting the default project, gcloud commands may run against the wrong project or fail.

Use --set-as-default flag during creation or run 'gcloud config set project PROJECT_ID' after.

Forgetting to enable required APIs after creating the project.

APIs are disabled by default; without enabling them, services like Compute Engine won't work.

Run 'gcloud services enable API_NAME' for each needed service.

Summary

Create a new GCP project with a unique ID and set it as default.

Set the active project explicitly to avoid running commands on the wrong project.

Describe the project to verify its details and status.

Enable necessary APIs to use cloud services within the project.

Practice

1. What is the main purpose of a project in Google Cloud Platform?

easy

A. To monitor internet traffic

B. To store user passwords securely

C. To group and organize cloud resources and settings

D. To create virtual machines automatically

Solution

1. Step 1: Understand the role of a project in GCP

   A project acts as a container that holds all your cloud resources and settings together.

2. Step 2: Identify the correct purpose

   Among the options, grouping and organizing resources is the key function of a project.

3. Final Answer:

   To group and organize cloud resources and settings -> Option C

4. Quick Check:

   Project groups resources = D [OK]

Hint: Projects group resources and settings simply [OK]

Common Mistakes:

• Confusing projects with user accounts
• Thinking projects create resources automatically
• Assuming projects monitor traffic

2. Which of the following is the correct way to set a default project using the gcloud CLI?

easy

A. gcloud default project [PROJECT_ID]

B. gcloud project set default [PROJECT_ID]

C. gcloud set project default [PROJECT_ID]

D. gcloud config set project [PROJECT_ID]

Solution

1. Step 1: Recall the gcloud command syntax for setting default project

   The correct command uses 'gcloud config set project' followed by the project ID.

2. Step 2: Compare options

   Only gcloud config set project [PROJECT_ID] matches the correct syntax exactly.

3. Final Answer:

   gcloud config set project [PROJECT_ID] -> Option D

4. Quick Check:

   Set default project with 'config set project' = C [OK]

Hint: Use 'gcloud config set project' to set default [OK]

Common Mistakes:

• Mixing command order or keywords
• Using 'project set default' instead of 'config set project'
• Omitting 'config' keyword

3. Given the following commands run in order:
gcloud config set project my-project-123
gcloud projects describe my-project-123
What will the second command do?

medium

A. Describe the project with ID 'my-project-123' regardless of default project

B. Describe the currently set default project

C. Fail because the project is not set as default

D. List all projects in the account

Solution

1. Step 1: Understand the commands

   The first command sets the default project to 'my-project-123'. The second command describes the project with the given ID explicitly.

2. Step 2: Analyze the behavior of 'gcloud projects describe'

   This command describes the project specified by the ID argument, independent of the default project setting.

3. Final Answer:

   Describe the project with ID 'my-project-123' regardless of default project -> Option A

4. Quick Check:

   'gcloud projects describe' uses given ID, not default project = A [OK]

Hint: 'gcloud projects describe' uses explicit ID, not default [OK]

Common Mistakes:

• Assuming 'describe' uses default project if ID given
• Thinking it lists all projects
• Believing it fails without default project

4. You tried to set the default project with the command:
gcloud set project my-project-123
But it failed. What is the most likely reason?

medium

A. The command syntax is incorrect; 'config' keyword is missing

B. The project ID does not exist

C. You need to be logged in first

D. The project is already set as default

Solution

1. Step 1: Check the command syntax

   The correct command to set default project is 'gcloud config set project [PROJECT_ID]'. The given command misses the 'config' keyword.

2. Step 2: Evaluate other options

   While login and project existence matter, the error is most likely due to wrong syntax here.

3. Final Answer:

   The command syntax is incorrect; 'config' keyword is missing -> Option A

4. Quick Check:

   Missing 'config' in command causes failure = A [OK]

Hint: Remember 'gcloud config set project' syntax [OK]

Common Mistakes:

• Omitting 'config' keyword
• Assuming project existence error without checking syntax
• Ignoring login status

5. You want to create a new project with a unique ID and a friendly name using the gcloud CLI. Which command correctly achieves this?

hard

A. gcloud create project my-new-project --display-name="My Friendly Project"

B. gcloud projects create my-new-project --name="My Friendly Project"

C. gcloud projects new my-new-project --label="My Friendly Project"

D. gcloud project create --id=my-new-project --name="My Friendly Project"

Solution

1. Step 1: Recall the correct command to create a project

   The correct syntax is 'gcloud projects create [PROJECT_ID] --name="Friendly Name"'.

2. Step 2: Compare options to the correct syntax

   Only gcloud projects create my-new-project --name="My Friendly Project" matches the correct command and flag usage.

3. Final Answer:

   gcloud projects create my-new-project --name="My Friendly Project" -> Option B

4. Quick Check:

   Create project with 'projects create' and --name flag = B [OK]

Hint: Use 'gcloud projects create' with --name for friendly name [OK]

Common Mistakes:

• Using wrong command order or flags
• Confusing 'project' and 'projects' commands
• Using --display-name or --label instead of --name