Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support enabling auth plugins with vault_auth_backend #54

Closed
tomwilkie opened this issue Jan 11, 2018 · 4 comments
Closed

Support enabling auth plugins with vault_auth_backend #54

tomwilkie opened this issue Jan 11, 2018 · 4 comments

Comments

@tomwilkie
Copy link

The plugin_name field needs to be supplied.

Terraform Version

$ terraform -v
Terraform v0.10.8

Affected Resource(s)

  • vault_auth_backend
@tomwilkie
Copy link
Author

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
Copy link

michaeljs1990 commented Jul 30, 2019

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
Copy link

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
Copy link
Contributor

closed by hashicorp/vault#5536

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants