IAM policy for GCE subnetwork

Three different resources help you manage your IAM policy for GCE subnetwork. Each of these resources serves a different use case:

google_compute_subnetwork_iam_policy

data "google_iam_policy" "admin" {
  binding {
    role = "roles/editor"

    members = [
      "user:[email protected]",
    ]
  }
}

resource "google_compute_subnetwork_iam_policy" "subnet" {
    subnetwork  = "your-subnetwork-id"
    policy_data = "${data.google_iam_policy.admin.policy_data}"
}

google_compute_subnetwork_iam_binding

resource "google_compute_subnetwork_iam_binding" "subnet" {
  subnetwork = "your-subnetwork-id"
  role       = "roles/compute.networkUser"

  members = [
    "user:[email protected]",
  ]
}

google\compute_subnetwork_iam_member

resource "google_compute_subnetwork_iam_member" "subnet" {
  subnetwork = "your-subnetwork-id"
  role       = "roles/compute.networkUser"
  member     = "user:[email protected]"
}

Argument Reference

The following arguments are supported:

  • subnetwork - (Required) The name of the subnetwork.

  • member/members - (Required) Identities that will be granted the privilege in role. Each entry can have one of the following values:

    • allUsers: A special identifier that represents anyone who is on the internet; with or without a Google account.
    • allAuthenticatedUsers: A special identifier that represents anyone who is authenticated with a Google account or a service account.
    • user:{emailid}: An email address that represents a specific Google account. For example, [email protected] or [email protected].
    • serviceAccount:{emailid}: An email address that represents a service account. For example, [email protected].
    • group:{emailid}: An email address that represents a Google group. For example, [email protected].
    • domain:{domain}: A Google Apps domain name that represents all the users of that domain. For example, google.com or example.com.
  • role - (Required) The role that should be applied. Only one google_compute_subnetwork_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_compute_subnetwork_iam_policy) The policy data generated by a google_iam_policy data source.

  • project - (Optional) The ID of the project in which the resource belongs. If it is not provided, the provider project is used.

  • region - (Optional) The region of the subnetwork. If unspecified, this defaults to the region configured in the provider.

Attributes Reference

In addition to the arguments listed above, the following computed attributes are exported:

  • etag - (Computed) The etag of the subnetwork's IAM policy.

Import

For all import syntaxes, the "resource in question" can take any of the following forms:

  • full self link or relative link (projects/{{project}}/region/{{region}}/subnetworks/{{name}})
  • {{project}}/{{region}}/{{name}}
  • {{region}}/{{name}} (project is taken from provider project)
  • {{name}} (project and region are taken from provider project)

IAM member imports use space-delimited identifiers; the resource in question, the role, and the account, e.g.

$ terraform import google_compute_subnetwork_iam_member.subnet "project-name/region-name/subnetwork-name roles/compute.networkUser [email protected]"

IAM binding imports use space-delimited identifiers; the resource in question and the role, e.g.

$ terraform import google_compute_subnetwork_iam_binding.subnet "project-name/region-name/subnetwork-name roles/compute.networkUser"

IAM policy imports use the identifier of the resource in question, e.g.

$ terraform import google_compute_subnetwork_iam_policy.subnet project-name/region-name/subnetwork-name

© 2018 HashiCorp
Licensed under the MPL 2.0 License.
https://www.terraform.io/docs/providers/google/r/compute_subnetwork_iam.html