From 459436fd20b5d98e3f587a7ad041a5bc8d49361b Mon Sep 17 00:00:00 2001 From: Richard Hsu Date: Wed, 8 May 2019 12:11:48 -0400 Subject: [PATCH] fixing typos and roles --- website/docs/r/compute_instance_iam.html.markdown | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/website/docs/r/compute_instance_iam.html.markdown b/website/docs/r/compute_instance_iam.html.markdown index a247f934..9c54414e 100644 --- a/website/docs/r/compute_instance_iam.html.markdown +++ b/website/docs/r/compute_instance_iam.html.markdown @@ -42,7 +42,7 @@ resource "google_compute_instance_iam_policy" "instance" { ```hcl resource "google_compute_instance_iam_binding" "instance" { instance_name = "your-instance-name" - role = "roles/compute.osLoginr" + role = "roles/compute.osLogin" members = [ "user:jane@example.com", @@ -107,13 +107,13 @@ For all import syntaxes, the "resource in question" can take any of the followin IAM member imports use space-delimited identifiers; the resource in question, the role, and the member identity, e.g. ``` -$ terraform import google_compute_instance_iam_member.instance "project-name/zone-name/instance-name roles/compute.networkUser user:foo@example.com" +$ terraform import google_compute_instance_iam_member.instance "project-name/zone-name/instance-name roles/compute.osLogin user:foo@example.com" ``` IAM binding imports use space-delimited identifiers; the resource in question and the role, e.g. ``` -$ terraform import google_compute_instance_iam_binding.instance "project-name/zone-name/instance-name roles/compute.networkUser" +$ terraform import google_compute_instance_iam_binding.instance "project-name/zone-name/instance-name roles/compute.osLogin" ``` IAM policy imports use the identifier of the resource in question, e.g.