-
Notifications
You must be signed in to change notification settings - Fork 549
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 configuring plugins in Vault's plugin catalog #214
Comments
It's ugly, but you can work around this by using: resource "vault_generic_secret" "plugin_registration" {
path = "sys/plugins/catalog/my-plugin-name"
disable_read = true
data_json = <<-EOF
{
"sha_256": "...",
"command": "my-plugin-command"
}
EOF
} |
Similarly, we use this: resource "vault_generic_endpoint" "plugin_name" {
disable_read = false
disable_delete = true
path = "sys/plugins/catalog/secret/pluginname"
ignore_absent_fields = true
data_json = jsonencode({
sha_256 = "aaaaaaaaaaaaaaaaaaaaaaaaaaaa..."
command = "pluginname_v1"
})
} |
With the new versioned plugins, a simple REF: https://gist.github.com/TJM/c5600ee1902762e8bba7915b74084ad8 USE AT YOUR OWN RISK! |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Terraform Version
Affected Resource(s)
A suitable resource does not exist yet.
Terraform Configuration Files
N/A
Debug Output
N/A
Panic Output
N/A
Expected Behavior
There should be a resource type to add plugins to Vault's plugin catalog. This process is described in this blog post: https://www.hashicorp.com/blog/building-a-vault-secure-plugin
The main thing I am asking for here is native support for writing to the plugin catalog, like:
vault write sys/plugins/catalog/my-plugin command=my-plugin sha256=fc1c3225364b5cdb570c0b1e7be8ebf2725bdabf472c86e4095b4880083606a3
Such a resource could be called something like
vault_plugin
orvault_catalog_plugin
.It is possible to approximate this with the
vault_generic_secret
resource.Actual Behavior
There is not such a resource type.
Steps to Reproduce
N/A
References
The text was updated successfully, but these errors were encountered: