Creates a billing account.
This method can only be used to create
billing subaccounts
by GCP resellers.
When creating a subaccount, the current authenticated user must have the
billing.accounts.update IAM permission on the master account, which is
typically given to billing account
administrators.
This method will return an error if the master account has not been
provisioned as a reseller account.
Gets the access control policy for a billing account.
The caller must have the billing.accounts.getIamPolicy permission on the
account, which is often given to billing account
viewers.
Lists the projects associated with a billing account. The current
authenticated user must have the billing.resourceAssociations.list IAM
permission, which is often given to billing account
viewers.
Sets the access control policy for a billing account. Replaces any existing
policy.
The caller must have the billing.accounts.setIamPolicy permission on the
account, which is often given to billing account
administrators.
Tests the access control policy for a billing account. This method takes
the resource and a set of permissions as input and returns the subset of
the input permissions that the caller is allowed for that resource.
Updates a billing account's fields.
Currently the only field that can be edited is display_name.
The current authenticated user must have the billing.accounts.update
IAM permission, which is typically given to the
administrator
of the billing account.
Sets or updates the billing account associated with a project. You specify
the new billing account by setting the billing_account_name in the
ProjectBillingInfo resource to the resource name of a billing account.
Associating a project with an open billing account enables billing on the
project and allows charges for resource usage. If the project already had a
billing account, this method changes the billing account used for resource
usage charges.
Note: Incurred charges that have not yet been reported in the transaction
history of the GCP Console might be billed to the new billing
account, even if the charge occurred before the new billing account was
assigned to the project.
The current authenticated user must have ownership privileges for both the
project and the billing
account.
You can disable billing on the project by setting the
billing_account_name field to empty. This action disassociates the
current billing account from the project. Any billable activity of your
in-use services will stop, and your application could stop functioning as
expected. Any unbilled charges to date will be billed to the previously
associated account. The current authenticated user must be either an owner
of the project or an owner of the billing account for the project.
Note that associating a project with a closed billing account will have
much the same effect as disabling billing on the project: any paid
resources used by the project will be shut down. Thus, unless you wish to
disable billing, you should always call this method with the name of an
open billing account.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-01-27 UTC."],[],[]]
