Difference between revisions of "Gcloud config set project"
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
gcloud config set project YOUR_PROJECT_NAME_CASE_SENSITIVE | gcloud config set project YOUR_PROJECT_NAME_CASE_SENSITIVE | ||
Updated property [core/project]. | Updated property [core/project]. | ||
| + | |||
| + | gcloud config set project YOUR-PROJECT | ||
| + | WARNING: You do not appear to have access to project [YOUR-PROJECT] or it does not exist. | ||
| + | Are you sure you wish to set property [core/project] to elucidate-co? | ||
| + | |||
| + | Do you want to continue (Y/n)? | ||
Revision as of 14:12, 27 September 2022
gcloud config set project YOUR_PROJECT_NAME_CASE_SENSITIVE
gcloud config set project YOUR_PROJECT_NAME_CASE_SENSITIVE Updated property [core/project].
gcloud config set project YOUR-PROJECT WARNING: You do not appear to have access to project [YOUR-PROJECT] or it does not exist. Are you sure you wish to set property [core/project] to elucidate-co? Do you want to continue (Y/n)?
gcloud compute images list ERROR: (gcloud.compute.images.list) The required property [project] is not currently set. It can be set on a per-command basis by re-running your command with the [--project] flag. You may set it for your current workspace by running: $ gcloud config set project VALUE or it can be set temporarily by the environment variable [CLOUDSDK_CORE_PROJECT]
Related
See also
gcloud config set: [account | compute | project | disable prompts]gcloud config[set | list | get-value | configurations | --help],~/.config/gcloud/, gcloud config set account
Advertising:
