You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
According to current documentation (https://github.com/hashicorp/vault/blob/main/website/content/docs/configuration/storage/postgresql.mdx vault cannot create tables automatically. I use helm chart from bank vault to deploy vault (https://github.com/bank-vaults/vault-helm-chart). At the moment I am unfolding the tables manually. When deploying manually, the first installation always fails, because vault initially creates roles, users and a vault database in PostgreSQL, and then creates tables on top of that. Pre-installation in PostgreSQL is difficult because user credentials created before helm deployment will have different passwords and the application will not be able to get into the database (to create tables, the vault_owner_user user is used, which is automatically created when helm is deployed, and the password is put in secrets).
Describe the solution you'd like
Automatically add tables (vault_kv_store, vault_ha_locks) and function (vault_kv_put) when selecting postgresql as secret storage.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
According to current documentation (https://github.com/hashicorp/vault/blob/main/website/content/docs/configuration/storage/postgresql.mdx vault cannot create tables automatically. I use helm chart from bank vault to deploy vault (https://github.com/bank-vaults/vault-helm-chart). At the moment I am unfolding the tables manually. When deploying manually, the first installation always fails, because vault initially creates roles, users and a vault database in PostgreSQL, and then creates tables on top of that. Pre-installation in PostgreSQL is difficult because user credentials created before helm deployment will have different passwords and the application will not be able to get into the database (to create tables, the vault_owner_user user is used, which is automatically created when helm is deployed, and the password is put in secrets).
Describe the solution you'd like
Automatically add tables (vault_kv_store, vault_ha_locks) and function (vault_kv_put) when selecting postgresql as secret storage.
The text was updated successfully, but these errors were encountered: