Folders for grouping projects in GCP - Commands & Configuration

Introduction

When you have many projects in Google Cloud, it can get messy to manage them all. Folders help you group projects together so you can organize and control them easily.

When you want to organize projects by department like sales, marketing, or engineering.

When you need to apply the same access rules to multiple projects at once.

When you want to see billing or usage grouped by teams or business units.

When you want to separate projects for different environments like development, testing, and production.

When you want to keep related projects together for easier management and reporting.

Commands

This command creates a folder named Engineering under your organization with ID 123456789012. Folders help group projects.

Terminal

gcloud resource-manager folders create --display-name="Engineering" --organization=123456789012

Expected Output

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

displayName: Engineering

name: folders/987654321

parent: organizations/123456789012

state: ACTIVE

→

--display-name - Sets the name of the folder you want to create.

→

--organization - Specifies the organization under which the folder is created.

This command moves the project named my-project into the folder with ID 987654321 to group it under Engineering.

Terminal

gcloud projects move my-project --folder=987654321

Expected Output

Move request issued for project [my-project].

→

--folder - Specifies the folder ID where the project will be moved.

This command lists all folders under your organization so you can see your folder structure.

Terminal

gcloud resource-manager folders list --organization=123456789012

Expected Output

NAME              DISPLAY_NAME

folders/987654321 Engineering

→

--organization - Shows folders only under the specified organization.

This command lists all projects inside the Engineering folder to verify your grouping.

Terminal

gcloud projects list --filter="parent.id=987654321" --format="table(projectId, name)"

Expected Output

PROJECT_ID  NAME

my-project  My Project

→

--filter - Filters projects by their parent folder ID.

→

--format - Formats the output as a table for easy reading.

Key Concept

If you remember nothing else from this pattern, remember: folders let you organize and control multiple projects together under your Google Cloud organization.

Common Mistakes

Trying to create a folder without specifying the organization ID.

Folders must belong to an organization, so the command fails without it.

Always include the --organization flag with your organization's numeric ID when creating folders.

Moving a project to a folder using the folder name instead of the folder ID.

The move command requires the folder's numeric ID, not its display name.

Use the folder ID (like 987654321) with the --folder flag when moving projects.

Not verifying the folder or project move by listing folders or projects afterward.

You might think the operation succeeded but it could have failed silently or with a warning.

Always run list commands to confirm your folders and projects are organized as expected.

Summary

Create folders under your organization to group related projects.

Move projects into folders using their folder IDs to organize them.

List folders and projects to verify your cloud resource structure.

Practice

1. What is the main purpose of using folders in Google Cloud Platform (GCP)?

easy

A. To create user accounts

B. To group projects for better organization and management

C. To run virtual machines

D. To store files and data like a hard drive

Solution

1. Step 1: Understand folder function in GCP

   Folders are used to group projects logically under an organization or other folders.

2. Step 2: Compare folder purpose with other options

   Folders do not store data, run machines, or create users; those are different services.

3. Final Answer:

   To group projects for better organization and management -> Option B

4. Quick Check:

   Folders organize projects = D [OK]

Hint: Folders group projects, not store data or run machines [OK]

Common Mistakes:

• Confusing folders with storage buckets
• Thinking folders create users
• Assuming folders run virtual machines

2. Which gcloud command correctly creates a folder named Finance under an organization with ID 123456789?

easy

A. gcloud resource-manager folders create --name=Finance --parent=123456789

B. gcloud projects create Finance --organization=123456789

C. gcloud resource-manager folders create --display-name=Finance --organization=123456789

D. gcloud folders create --display-name=Finance --org=123456789

Solution

1. Step 1: Identify correct command syntax for folder creation

   The correct command uses gcloud resource-manager folders create with --display-name and --organization flags.

2. Step 2: Check options for correct flags and command structure

   gcloud resource-manager folders create --display-name=Finance --organization=123456789 matches the correct syntax; others use wrong flags or commands.

3. Final Answer:

   gcloud resource-manager folders create --display-name=Finance --organization=123456789 -> Option C

4. Quick Check:

   Correct gcloud folder create syntax = A [OK]

Hint: Use 'resource-manager folders create' with --display-name and --organization [OK]

Common Mistakes:

• Using 'gcloud projects create' instead of folders
• Using incorrect flags like --name or --org
• Omitting the parent organization flag

3. Given this command:
gcloud resource-manager folders create --display-name=Dev --folder=987654321
What is the parent of the new folder named Dev?

medium

A. Folder with ID 987654321

B. Project with ID 987654321

C. Organization with ID 987654321

D. No parent specified

Solution

1. Step 1: Understand the meaning of --folder flag

   The --folder flag specifies the parent folder ID under which the new folder is created.

2. Step 2: Identify the parent type from the flag

   Since --folder=987654321 is used, the parent is a folder with that ID, not an organization or project.

3. Final Answer:

   Folder with ID 987654321 -> Option A

4. Quick Check:

   --folder flag sets parent folder = C [OK]

Hint: --folder flag means parent is a folder, not organization [OK]

Common Mistakes:

• Confusing --folder with --organization
• Assuming parent is a project
• Ignoring the parent flag

4. You run this command:
gcloud resource-manager folders create --display-name=HR --parent=organizations/123456789
But get an error. What is the likely cause?

medium

A. The user lacks permission to create folders under the organization

B. The flag --parent is invalid; use --organization instead

C. The command requires --folder flag, not --parent

D. The organization ID is incorrect format; should be numeric only

Solution

1. Step 1: Check command syntax for folder creation

   The --parent flag is valid and can accept organization or folder resource names.

2. Step 2: Consider permission issues

   If the command syntax is correct but fails, the most common cause is insufficient permissions to create folders under the organization.

3. Final Answer:

   The user lacks permission to create folders under the organization -> Option A

4. Quick Check:

   Permission errors cause folder creation failure = B [OK]

Hint: Check permissions if syntax and IDs are correct [OK]

Common Mistakes:

• Assuming --parent flag is invalid
• Thinking organization ID format is wrong
• Confusing --folder and --parent flags

5. You want to organize projects for two departments, Sales and Engineering, under your organization. You also want to apply different billing accounts and permissions to each department easily. What is the best way to set this up using folders?

hard

A. Create one folder for all projects and use labels to separate Sales and Engineering

B. Create projects named Sales and Engineering directly under the organization without folders

C. Create billing accounts named Sales and Engineering and assign projects to them without folders

D. Create two folders named Sales and Engineering under the organization, then move projects into each folder

Solution

1. Step 1: Understand folder benefits for grouping and management

   Folders allow grouping projects logically and applying permissions and billing at folder level.

2. Step 2: Evaluate options for organizing projects by department

   Creating separate folders for Sales and Engineering under the organization lets you manage billing and permissions easily per department.

3. Step 3: Compare with other options

   Projects without folders or using labels do not provide folder-level permission and billing management. Billing accounts alone do not organize projects.

4. Final Answer:

   Create two folders named Sales and Engineering under the organization, then move projects into each folder -> Option D

5. Quick Check:

   Folders group projects for billing and permissions = A [OK]

Hint: Use folders per department for easy billing and permission control [OK]

Common Mistakes:

• Skipping folders and relying on labels only
• Assigning billing without folder structure
• Creating projects without grouping