Support enabling auth plugins with vault_auth_backend

[hashicorp]

Support enabling auth plugins with vault_auth_backend

[tomwilkie]

It can be worked around with eg:

resource "vault_generic_secret" "google_plugin_enable" {
  depends_on   = ["vault_generic_secret.google_plugin_sha"]
  path         = "sys/auth/google"
  disable_read = true

  data_json = <<EOF
{
  "type": "plugin",
  "plugin_name": "google-auth-vault-plugin"
}
EOF
}

But its a bit of a hack...

[michaeljs1990]

It seems like #214 would the final solution to this since plugins do have their own endpoints. This is a fairly annoying thing right now and everyone writing plugins ideally shouldn't have to write a custom TF resource to match it.

[michaeljs1990]

This can actually be closed out now. hashicorp/vault#5536 fixes this and going off the above example lets you write the following tf. Thanks for the work on this @tyrannosaurus-becks.

resource "vault_auth_backend" "google_plugin_enable" {
  type = "google-auth-vault-plugin"
}

[fairclothjm]

closed by hashicorp/vault#5536