Add IAP Tunnel Instance Docs (#3593)

Signed-off-by: Modular Magician <magic-modules@google.com>
This commit is contained in:
The Magician 2019-05-08 14:11:48 -07:00 committed by Riley Karson
parent 189a617987
commit b24ee24d28
4 changed files with 133 additions and 0 deletions

View File

@ -0,0 +1,3 @@
package google
// Magic Modules doesn't let us remove files - blank out beta-only common-compile files for now.

View File

@ -0,0 +1,3 @@
package google
// Magic Modules doesn't let us remove files - blank out beta-only common-compile files for now.

View File

@ -0,0 +1,126 @@
---
layout: "google"
page_title: "Google: google_iap_tunnel_instance_iam"
sidebar_current: "docs-google-iap-tunnel-instance-iam"
description: |-
Collection of resources to manage IAM policy for a IAP Tunnel Instance.
---
# IAM policy for IAP Tunnel Instance
~> **Warning:** These resources are in beta, and should be used with the terraform-provider-google-beta provider.
See [Provider Versions](https://terraform.io/docs/providers/google/provider_versions.html) for more details on beta resources.
Three different resources help you manage your IAM policy for IAP Tunnel Instance. Each of these resources serves a different use case:
* `google_iap_tunnel_instance_iam_policy`: Authoritative. Sets the IAM policy for the instance and replaces any existing policy already attached.
* `google_iap_tunnel_instance_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 instance are preserved.
* `google_iap_tunnel_instance_iam_member`: Non-authoritative. Updates the IAM policy to grant a role to a new member. Other members for the role for the instance are preserved.
~> **Note:** `google_iap_tunnel_instance_iam_policy` **cannot** be used in conjunction with `google_iap_tunnel_instance_iam_binding` and `google_iap_tunnel_instance_iam_member` or they will fight over what your policy should be.
~> **Note:** `google_iap_tunnel_instance_iam_binding` resources **can be** used in conjunction with `google_iap_tunnel_instance_iam_member` resources **only if** they do not grant privilege to the same role.
## google\_iap\_tunnel\_instance\_iam\_policy
```hcl
data "google_iam_policy" "admin" {
binding {
role = "roles/editor"
members = [
"user:jane@example.com",
]
}
}
resource "google_iap_tunnel_instance_iam_policy" "instance" {
instance = "your-instance-name"
policy_data = "${data.google_iam_policy.admin.policy_data}"
}
```
## google\_iap\_tunnel\_instance\_iam\_binding
```hcl
resource "google_iap_tunnel_instance_iam_binding" "instance" {
instance = "your-instance-name"
role = "roles/compute.networkUser"
members = [
"user:jane@example.com",
]
}
```
## google\_iap\_tunnel\_instance\_iam\_member
```hcl
resource "google_iap_tunnel_instance_iam_member" "instance" {
instance = "your-instance-name"
role = "roles/compute.networkUser"
member = "user:jane@example.com"
}
```
## Argument Reference
The following arguments are supported:
* `instance` - (Required) The name of the instance.
* `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, alice@gmail.com or joe@example.com.
* **serviceAccount:{emailid}**: An email address that represents a service account. For example, my-other-app@appspot.gserviceaccount.com.
* **group:{emailid}**: An email address that represents a Google group. For example, admins@example.com.
* **domain:{domain}**: A G Suite domain (primary, instead of alias) 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_iap_tunnel_instance_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_iap_tunnel_instance_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.
* `zone` - (Optional) The zone of the instance. If
unspecified, this defaults to the zone 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 instance'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}}/zones/{{zone}}/instances/{{name}})
* {{project}}/{{zone}}/{{name}}
* {{zone}}/{{name}} (project is taken from provider project)
* {{name}} (project and zone are taken from provider project)
IAM member imports use space-delimited identifiers; the resource in question, the role, and the member identity, e.g.
```
$ terraform import google_iap_tunnel_instance_iam_member.instance "project-name/zone-name/instance-name roles/compute.networkUser user:foo@example.com"
```
IAM binding imports use space-delimited identifiers; the resource in question and the role, e.g.
```
$ terraform import google_iap_tunnel_instance_iam_binding.instance "project-name/zone-name/instance-name roles/compute.networkUser"
```
IAM policy imports use the identifier of the resource in question, e.g.
```
$ terraform import google_iap_tunnel_instance_iam_policy.instance project-name/zone-name/instance-name
```

View File

@ -635,6 +635,7 @@
</ul>
</li>
<li<%= sidebar_current("docs-google-pubsub") %>>
<a href="#">Google PubSub Resources</a>
<ul class="nav nav-visible">