Configuration properties in GCP - Mini Project: Build & Apply

GCP Configuration Properties Setup

📖 Scenario: You are setting up a Google Cloud Platform (GCP) project configuration to manage environment-specific properties for a web application deployment.

🎯 Goal: Build a configuration file that holds key properties such as project ID, region, and environment type, then use these properties to define deployment settings.

📋 What You'll Learn

Create a dictionary named config with specific keys and values

Add a variable environment to select the deployment environment

Use the environment variable to set the config dictionary's project_id accordingly

Add a final property deployment_name that combines environment and region

💡 Why This Matters

🌍 Real World

Managing configuration properties is essential for deploying cloud applications in different environments like development, testing, and production.

💼 Career

Cloud engineers and DevOps professionals often create and manage configuration files to automate deployments and maintain consistency across environments.

1

Create initial configuration dictionary

Create a dictionary called config with these exact entries: 'project_id': 'my-gcp-project', 'region': 'us-central1', and 'environment': 'dev'.

GCP

# Create the config dictionary with project_id, region, and environment
# Your code here

Hint

Use curly braces to create a dictionary and separate keys and values with colons.

2

Add environment variable

Create a variable called environment and set it to the string 'prod'.

GCP

config = {
    'project_id': 'my-gcp-project',
    'region': 'us-central1',
    'environment': 'dev'
}
# Create the environment variable and set it to 'prod'
# Your code here

Hint

Assign the string 'prod' to the variable named environment.

3

Update project_id based on environment

Use an if statement to check if environment equals 'prod'. If true, update config['project_id'] to 'my-gcp-project-prod'. Otherwise, keep it as 'my-gcp-project'.

GCP

config = {
    'project_id': 'my-gcp-project',
    'region': 'us-central1',
    'environment': 'dev'
}
environment = 'prod'
# Update config['project_id'] based on environment
# Your code here

Hint

Use an if-else block to update the project_id in the config dictionary.

4

Add deployment_name property

Add a new key 'deployment_name' to the config dictionary. Set its value to a string combining environment and config['region'] separated by a dash, like prod-us-central1.

GCP

config = {
    'project_id': 'my-gcp-project',
    'region': 'us-central1',
    'environment': 'dev'
}
environment = 'prod'
if environment == 'prod':
    config['project_id'] = 'my-gcp-project-prod'
else:
    config['project_id'] = 'my-gcp-project'
# Add deployment_name to config combining environment and region
# Your code here

Hint

Use an f-string to combine environment and region with a dash.

Practice

1. What is the purpose of configuration properties in Google Cloud Platform (GCP)?

easy

A. To define settings that control how cloud resources behave

B. To write application code for cloud functions

C. To store user data in databases

D. To monitor network traffic in real-time

Solution

1. Step 1: Understand configuration properties

   Configuration properties are settings that control the behavior of cloud resources like virtual machines, storage, or services.

2. Step 2: Differentiate from other cloud tasks

   Writing code, storing data, or monitoring traffic are different tasks not directly related to configuration properties.

3. Final Answer:

   To define settings that control how cloud resources behave -> Option A

4. Quick Check:

   Configuration properties = settings control behavior [OK]

Hint: Think of configuration as setting rules for cloud resources [OK]

Common Mistakes:

• Confusing configuration with coding
• Mixing configuration with data storage
• Assuming configuration monitors traffic

2. Which of the following is the correct way to specify a configuration property in a GCP YAML deployment file?

easy

A. config:
instanceType = n1-standard-1

B. properties:
instanceType: n1-standard-1

C. settings:
instanceType: 'n1-standard-1'

D. parameters:
instanceType -> n1-standard-1

Solution

1. Step 1: Identify correct YAML syntax for properties

   In GCP deployment manager, configuration properties are under 'properties:' with key-value pairs using colon and indentation.

2. Step 2: Check each option's syntax

   properties: instanceType: n1-standard-1 uses 'properties:' and colon syntax correctly. Options B, C, and D use incorrect keys or invalid syntax like '=' or '->'.

3. Final Answer:

   properties: instanceType: n1-standard-1 -> Option B

4. Quick Check:

   YAML properties use colon and indentation [OK]

Hint: YAML uses colon and indentation for key-value pairs [OK]

Common Mistakes:

• Using '=' instead of ':' in YAML
• Wrong top-level key like 'config' or 'settings'
• Using symbols like '->' which are invalid in YAML

3. Given this snippet of a GCP deployment YAML:

resources:
- name: my-vm
  type: compute.v1.instance
  properties:
    zone: us-central1-a
    machineType: zones/us-central1-a/machineTypes/n1-standard-1
    disks:
    - deviceName: boot
      type: PERSISTENT
      boot: true
      autoDelete: true
      initializeParams:
        sourceImage: projects/debian-cloud/global/images/family/debian-10

What is the machine type configured for the VM?

medium

A. n1-standard-1

B. us-central1-a

C. debian-10

D. PERSISTENT

Solution

1. Step 1: Locate machineType property

   The machineType is set under properties as 'zones/us-central1-a/machineTypes/n1-standard-1'. The last part after the last slash is the machine type.

2. Step 2: Extract machine type value

   The machine type is 'n1-standard-1', which defines the VM size and resources.

3. Final Answer:

   n1-standard-1 -> Option A

4. Quick Check:

   Machine type is the last part of the path [OK]

Hint: Machine type is the last segment in the machineTypes path [OK]

Common Mistakes:

• Confusing zone with machine type
• Picking image name as machine type
• Selecting disk type as machine type

4. You have this GCP deployment YAML snippet:

resources:
- name: my-storage
  type: storage.v1.bucket
  properties:
    location: us-east1
    storageClass: STANDARD
    versioning:
      enabled: true
    accessControl:
      - entity: allUsers
        role: READER

What is the error in this configuration?

medium

A. location must be a zone, not a region

B. versioning.enabled must be false for public buckets

C. accessControl should be acl

D. storageClass must be lowercase

Solution

1. Step 1: Check property names for storage bucket

   The correct property for access control in GCP storage buckets is 'acl', not 'accessControl'.

2. Step 2: Validate other properties

   Versioning can be true or false regardless of public access. StorageClass is case-insensitive but usually uppercase is accepted. Location is a region, which is correct.

3. Final Answer:

   accessControl should be acl -> Option C

4. Quick Check:

   Property names must match GCP specs exactly [OK]

Hint: Check exact property names in GCP docs [OK]

Common Mistakes:

• Using incorrect property name 'accessControl' instead of 'acl'
• Assuming versioning must be false for public buckets
• Confusing region and zone names

5. You want to configure a GCP Compute Engine instance with a startup script and custom metadata. Which configuration properties should you use in your deployment YAML to achieve this?

hard

A. startupScript: |
#!/bin/bash
echo Hello World

B. scripts:
startup: '#!/bin/bash\necho Hello World'

C. customMetadata:
startup-script: '#!/bin/bash\necho Hello World'

D. metadata:
items:
- key: startup-script
value: |-
#!/bin/bash
echo Hello World

Solution

1. Step 1: Identify correct metadata property for startup scripts

   GCP Compute Engine uses 'metadata' with 'items' list containing key-value pairs for custom metadata like 'startup-script'.

2. Step 2: Verify syntax for multiline script

   Using '|-' in YAML allows multiline script values correctly under 'value'. Other options use incorrect property names or formats.

3. Final Answer:

   metadata: items: - key: startup-script value: |- #!/bin/bash echo Hello World -> Option D

4. Quick Check:

   Use metadata.items with key startup-script [OK]

Hint: Startup scripts go under metadata.items with key 'startup-script' [OK]

Common Mistakes:

• Using wrong property names like startupScript or scripts
• Not formatting multiline scripts properly in YAML
• Placing script outside metadata block