Cloud Build Artifact Registry Substitutions Python

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

Your team is building a continuous integration pipeline in Cloud Build to package and publish Python libraries to Google Cloud Artifact Registry across different deployment environments (such as staging and production).

You need to create a reusable cloudbuild.yaml configuration that dynamically targets different repository locations and names without hardcoding values, while relying on Cloud Build's default variables for the project ID.

Which configuration and submission command should you use?

Define user-defined substitutions with leading underscores (${_LOCATION} and ${_REPOSITORY}) in cloudbuild.yaml with the default $PROJECT_ID variable, and submit using --substitutions=_LOCATION="us-east1",_REPOSITORY="my-repo".

Define user-defined substitutions without underscores (${LOCATION} and ${REPOSITORY}) in cloudbuild.yaml, and submit using --substitutions=LOCATION="us-east1",REPOSITORY="my-repo".

Use container-level environment variables (env) inside the cloudbuild.yaml steps instead of substitutions, and pass variable overrides via the --build-arg flag in gcloud builds submit.

Define ${_LOCATION}, ${_REPOSITORY}, and ${_PROJECT_ID} as mandatory custom substitutions in cloudbuild.yaml, and pass all three parameters in the --substitutions flag during gcloud builds submit.

Professional Cloud DevOps Engineer

Cloud Build Artifact Registry Substitutions Python

Related questions