-
Notifications
You must be signed in to change notification settings - Fork 540
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
Сan't choose custom database plugin in vault_database_secret_backend_connection #1519
Comments
Hi @everythings-gonna-be-alright , unfortunately the provider does not currently support configuring custom plugins. We may add support in the future but we would not be able to provide an estimate on when that would be. |
@benashz Thanks for your answer. It can be useful for some cases in my view.
|
We could perhaps add a new db engine type |
@benashz the problem with current implementation is that is incompatible with HCP Vault Oracle Plugin. It's an embarrassing situation because Oracle database are supported officially by the provider and by HCP Vault. |
@manobi Hi, can you try setting plugin_name to be |
@fairclothjm I've tried, but got the following error reproduced by HCP support engineers.
The support team referenced this issue and the If you have access to it, my case is present on Hashicorp Help Center #121682. |
This is indeed embarrassing and for whatever reason it works when using |
Is this issue fixed? I am using vault-plugin-database-oracle as the plugin_name in vault_database_secret_backend_connection but it default to oracle-database-plugin |
terraform-provider-vault/vault/resource_database_secret_backend_connection.go
Line 103 in 24044c4
I'm trying to add my own clickhouse plugin but can't do it because of this architecture issue.
Error:
│ Error: unsupported database plugin name "clickhouse-database-plugin", must begin with one of: elasticsearch, mysql-legacy, mongodbatlas, mysql-aurora, postgresql, mysql-rds, couchbase, cassandra, snowflake, influxdb, redshift, mongodb, oracle, mssql, mysql, hana
Example without terraform:
The text was updated successfully, but these errors were encountered: