imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-16 12:22:03 +00:00
Code Activity

gcloud: Wed Jul 26 10:48:49 UTC 2023

Browse source
This commit is contained in:
Automated 2023-07-26 10:48:49 +00:00
parent 64e67b443c
commit 4558a00e48
204 changed files with 2787 additions and 1591 deletions
Download patch file Download diff file Expand all files Collapse all files

4
gcloud/alpha/billing/projects/describe
View file

@ -30,6 +30,10 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
API REFERENCE
This command uses the cloudbilling/v1 API. The full documentation for this
API can be found at: https://cloud.google.com/billing/v1/getting-started
NOTES
This command is currently in alpha and might change without notice. If this
command fails with API permission errors despite specifying the correct

23
gcloud/alpha/billing/projects/link
View file

@ -7,11 +7,24 @@ SYNOPSIS
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) This command links a billing account to a project.
If the specified billing account is open, this enables billing on the
(ALPHA) This command sets or updates the billing account associated with a
project.
Billing is enabled on a project when the project is linked to a valid,
active Cloud Billing account. The billing account accrues charges for the
usage of resources in all of the linked projects. If the project is already
linked to a billing account, this command moves the project to the billing
account you specify, updating the billing account that is linked to the
project.
Note that associating a project with a closed billing account has the same
effect as disabling billing on the project: any paid resources in use by
the project are shut down, and your application stops functioning. Unless
you want to disable billing, you should always specify a valid, active
Cloud Billing account when you run this command. Learn how to confirm the
status of a Cloud Billing account at
https://cloud.google.com/billing/docs/how-to/verify-billing-enabled#billing_account_status
EXAMPLES
To link a billing account 0X0X0X-0X0X0X-0X0X0X with a project my-project,
run:
@ -46,6 +59,10 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
API REFERENCE
This command uses the cloudbilling/v1 API. The full documentation for this
API can be found at: https://cloud.google.com/billing/v1/getting-started
NOTES
This command is currently in alpha and might change without notice. If this
command fails with API permission errors despite specifying the correct

4
gcloud/alpha/billing/projects/list
View file

@ -66,6 +66,10 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
API REFERENCE
This command uses the cloudbilling/v1 API. The full documentation for this
API can be found at: https://cloud.google.com/billing/v1/getting-started
NOTES
This command is currently in alpha and might change without notice. If this
command fails with API permission errors despite specifying the correct

14
gcloud/alpha/billing/projects/unlink
View file

@ -6,8 +6,14 @@ SYNOPSIS
gcloud alpha billing projects unlink PROJECT_ID [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) This command unlinks a project from its linked billing account.
This disables billing on the project.
(ALPHA) This command unlinks a project from its associated billing account.
This action disables billing on the project. Any billable resources and
services in use in your project are stopped, and your application stops
functioning. Any costs accrued prior to disabling billing on the project
are charged to the previously associated billing account.
Note: To link a project to a different billing account, use the billing
projects link command. You do not need to unlink the project first.
EXAMPLES
To unlink the project my-project from its linked billing account, run:
@ -26,6 +32,10 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
API REFERENCE
This command uses the cloudbilling/v1 API. The full documentation for this
API can be found at: https://cloud.google.com/billing/v1/getting-started
NOTES
This command is currently in alpha and might change without notice. If this
command fails with API permission errors despite specifying the correct