Configuration properties in GCP - Commands & Configuration

Introduction

Configuration properties let you set values that control how your Google Cloud services behave. They help you customize your cloud resources without changing code.

When you want to set the region for your cloud resources to control where they run.

When you need to specify the project ID to tell gcloud which project to work with.

When you want to set default output formats for easier reading of command results.

When you want to configure authentication settings for your cloud commands.

When you want to switch between different configurations for different projects or environments.

Commands

This command shows the current configuration properties set in your gcloud environment.

Terminal

gcloud config list

Expected Output

[core]

account = [e-mail]

disable_usage_reporting = true

project = example-project



Your active configuration is: default

This command sets the active project to 'example-project' so that all future commands use this project by default.

Terminal

gcloud config set project example-project

Expected Output

Updated property [core/project].

This command sets the default compute region to 'us-east1' so resources will be created there unless specified otherwise.

Terminal

gcloud config set compute/region us-east1

Expected Output

Updated property [compute/region].

This command creates a new named configuration called 'test-config' to manage different sets of properties separately.

Terminal

gcloud config configurations create test-config

Expected Output

Created configuration [test-config].

This command switches the active configuration to 'test-config' so you can work with its specific settings.

Terminal

gcloud config configurations activate test-config

Expected Output

Activated configuration [test-config].

Key Concept

If you remember nothing else from this pattern, remember: configuration properties let you control your cloud environment settings easily without changing code.

Common Mistakes

Not setting the project property before running commands.

Commands may fail or run in the wrong project, causing confusion or errors.

Always set the project property with 'gcloud config set project your-project-id' before running commands.

Forgetting to activate the correct configuration when switching projects or environments.

You might run commands with the wrong settings, affecting unintended resources.

Use 'gcloud config configurations activate config-name' to switch to the right configuration before working.

Summary

Use 'gcloud config set' to set properties like project and region for your cloud commands.

Use 'gcloud config list' to see your current configuration settings.

Create and switch between configurations to manage different environments easily.