Three different resources help you manage IAM policies on billing accounts. Each of these resources serves a different use case:
google_billing_account_iam_policy
: Authoritative. Sets the IAM policy for the billing accounts and replaces any existing policy already attached.google_billing_account_iam_binding
: Authoritative for a given role. Updates the IAM policy to grant a role to a list of members. Other roles within the IAM policy for the table are preserved.google_billing_account_iam_member
: Non-authoritative. Updates the IAM policy to grant a role to a new member. Other members for the role of the billing accounts are preserved.data "google_iam_policy" "admin" {
binding {
role = "roles/billing.viewer"
members = [
"user:jane@example.com",
]
}
}
resource "google_billing_account_iam_policy" "editor" {
billing_account_id = "00AA00-000AAA-00AA0A"
policy_data = data.google_iam_policy.admin.policy_data
}
resource "google_billing_account_iam_binding" "editor" {
billing_account_id = "00AA00-000AAA-00AA0A"
role = "roles/billing.viewer"
members = [
"user:jane@example.com",
]
}
resource "google_billing_account_iam_member" "editor" {
billing_account_id = "00AA00-000AAA-00AA0A"
role = "roles/billing.viewer"
member = "user:jane@example.com"
}
The following arguments are supported:
billing_account_id
- (Required) The billing account id.For google_billing_account_iam_member
or google_billing_account_iam_binding
:
member/members
- (Required) Identities that will be granted the privilege in role
.
Each entry can have one of the following values:
role
- (Required) The role that should be applied. Only one
google_billing_account_iam_binding
can be used per role. Note that custom roles must be of the format
[projects|organizations]/{parent-name}/roles/{role-name}
. Read more about roles here.
google_billing_account_iam_policy
only:
policy_data
- (Required) The policy data generated by a google_iam_policy
data source.In addition to the arguments listed above, the following computed attributes are exported:
etag
- (Computed) The etag of the billing account's IAM policy.IAM member imports use space-delimited identifiers that contain the resource's billing_account_id
, role
, and member
. For example:
"{{billing_account_id}} roles/billing.user user:jane@example.com"
An import
block (Terraform v1.5.0 and later) can be used to import IAM members:
import {
id = "{{billing_account_id}} roles/billing.user user:jane@example.com"
to = google_billing_account_iam_member.default
}
The terraform import
command can also be used:
$ terraform import google_billing_account_iam_member.default "{{billing_account_id}} roles/billing.user user:jane@example.com"
IAM binding imports use space-delimited identifiers that contain the resource's billing_account_id
and role
. For example:
"{{billing_account_id}} roles/billing.user"
An import
block (Terraform v1.5.0 and later) can be used to import IAM bindings:
import {
id = "{{billing_account_id}} roles/billing.user"
to = google_billing_account_iam_binding.default
}
The terraform import
command can also be used:
$ terraform import google_billing_account_iam_binding.default "{{billing_account_id}} roles/billing.user"
IAM policy imports use the billing_account_id
identifier of the Billing Account resource only. For example:
{{billing_account_id}}
An import
block (Terraform v1.5.0 and later) can be used to import IAM policies:
import {
id = {{billing_account_id}}
to = google_billing_account_iam_policy.default
}
The terraform import
command can also be used:
$ terraform import google_billing_account_iam_policy.default {{billing_account_id}}