Question

A development team runs an automated shell script in Cloud Shell to create resources across several projects. The script relies on the default gcloud project configured in the active configuration. During a nightly batch run, resources were accidentally created in the wrong project because a teammate had earlier changed the active gcloud config. As the cloud architect, what should you advise the team to do to make the script safe and unambiguous regardless of the active configuration?

Accepted Answer

Explicitly pass the --project flag on every gcloud command in the script so the target project is never inferred from the active configuration.

Answer

Add a 'gcloud config set project' command at the start of the script so the active configuration is updated before resources are created.

Answer

Instruct all team members to avoid changing the active gcloud configuration while any batch job might be running.

Answer

Set the CLOUDSDK_CORE_PROJECT environment variable once in the user's shell profile so all sessions share the same default project.