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
{{ message }}
This repository has been archived by the owner on Nov 29, 2023. It is now read-only.
During development I'm using an in-memory Vault. One of the consequences is if Vault is restarted all of the contents are lost. The result is Postgres is referencing a path in Vault that no longer exists. If this happened with a more mature installation, verifying secrets for an organization could be a fire-drill
Development is a specific use-case, but in general I want to be able to save myself time dealing with secrets at an organization level.
Import secrets
Export secrets
Verify existing secrets exist at the path referenced in DB
The text was updated successfully, but these errors were encountered:
During development I'm using an in-memory Vault. One of the consequences is if Vault is restarted all of the contents are lost. The result is Postgres is referencing a path in Vault that no longer exists. If this happened with a more mature installation, verifying secrets for an organization could be a fire-drill
Development is a specific use-case, but in general I want to be able to save myself time dealing with secrets at an organization level.
The text was updated successfully, but these errors were encountered: