Three different resources help you manage your IAM policy for Cloud Deploy Target. Each of these resources serves a different use case:
google_clouddeploy_target_iam_policy
: Authoritative. Sets the IAM policy for the target and replaces any existing policy already attached.google_clouddeploy_target_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 target are preserved.google_clouddeploy_target_iam_member
: Non-authoritative. Updates the IAM policy to grant a role to a new member. Other members for the role for the target are preserved.A data source can be used to retrieve policy data in advent you do not need creation
google_clouddeploy_target_iam_policy
: Retrieves the IAM policy for the targetdata "google_iam_policy" "admin" {
binding {
role = "roles/viewer"
members = [
"user:jane@example.com",
]
}
}
resource "google_clouddeploy_target_iam_policy" "policy" {
project = google_clouddeploy_target.default.project
location = google_clouddeploy_target.default.location
name = google_clouddeploy_target.default.name
policy_data = data.google_iam_policy.admin.policy_data
}
resource "google_clouddeploy_target_iam_binding" "binding" {
project = google_clouddeploy_target.default.project
location = google_clouddeploy_target.default.location
name = google_clouddeploy_target.default.name
role = "roles/viewer"
members = [
"user:jane@example.com",
]
}
resource "google_clouddeploy_target_iam_member" "member" {
project = google_clouddeploy_target.default.project
location = google_clouddeploy_target.default.location
name = google_clouddeploy_target.default.name
role = "roles/viewer"
member = "user:jane@example.com"
}
The following arguments are supported:
name
- (Required) Used to find the parent resource to bind the IAM policy to
project
- (Optional) The ID of the project in which the resource belongs.
If it is not provided, the project will be parsed from the identifier of the parent resource. If no project is provided in the parent identifier and no project is specified, the provider project is used.
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_clouddeploy_target_iam_binding
can be used per role. Note that custom roles must be of the format
[projects|organizations]/{parent-name}/roles/{role-name}
.
policy_data
- (Required only by google_clouddeploy_target_iam_policy
) 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 IAM policy.For all import syntaxes, the "resource in question" can take any of the following forms:
Any variables not passed in the import command will be taken from the provider configuration.
Cloud Deploy target IAM resources can be imported using the resource identifiers, role, and member.
IAM member imports use space-delimited identifiers: the resource in question, the role, and the member identity, e.g.
$ terraform import google_clouddeploy_target_iam_member.editor "projects/{{project}}/locations/{{location}}/targets/{{target}} roles/viewer user:jane@example.com"
IAM binding imports use space-delimited identifiers: the resource in question and the role, e.g.
$ terraform import google_clouddeploy_target_iam_binding.editor "projects/{{project}}/locations/{{location}}/targets/{{target}} roles/viewer"
IAM policy imports use the identifier of the resource in question, e.g.
$ terraform import google_clouddeploy_target_iam_policy.editor projects/{{project}}/locations/{{location}}/targets/{{target}}
This resource supports User Project Overrides.