vault_gcp_auth_backend_role create fails when backend uses nested mount path.

[fore5fire]

Terraform Version

Terraform v0.13.4
+ provider registry.terraform.io/hashicorp/google v3.43.0
+ provider registry.terraform.io/hashicorp/nomad v1.4.9
+ provider registry.terraform.io/hashicorp/vault v2.14.0

Affected Resource(s)

• vault_gcp_auth_backend_role

Terraform Configuration Files

resource "vault_auth_backend" "gcp" {
  type = "gcp"
  path = "${var.env}/${var.region}/gpc"
}

resource "vault_gcp_auth_backend_role" "master" {
  role = "${var.playback_region}-${var.env}-master"
  type = "iam"

  backend                = vault_auth_backend.gcp.path
  bound_service_accounts = [var.master_service_account]
  token_policies         = [vault_policy.nomad_server.name]
}

Debug Output

https://gist.github.com/lsmith130/d763a5a0cd5b9ccf9a11da438e31613e

Panic Output

No crash

Expected Behavior

Should create a vault_gcp_auth_backend_role when backend uses a nested path.

Actual Behavior

terraform apply gave the error:

Error: invalid path "auth/test/usc1/gpc/role/usc1-test-master" for GCP auth backend role: Expected 4 parts in path 'auth/test/usc1/gpc/role/usc1-test-master'

Steps to Reproduce

1. terraform apply

Important Factoids

None

References

• vault_aws_auth_backend_client nested path support #459