-
Notifications
You must be signed in to change notification settings - Fork 1
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
Synchronization does not work. #12
Comments
In the debug output you have provided I do not see that |
Hi @pbchekin With the new helm chart everything worked, thank you very much! Question: is it possible to create My case: |
I understand that this is a valid use case, but looks like it is a Vault administration rather than secrets synchronization. To create a new secrets backend vault-sync needs to have additional privileges and a way to specify a backend parameters, if they differ from the default ones. After that you need to configure permissions for users to use a newly added backend. I would recommend to have a centralized configuration for Vault backends. I believe you have a code that deploys and initializes all that Vault instances, it is a good place to create all these backends and set permissions for the users. This Terraform provider worked for me in the past: https://registry.terraform.io/providers/hashicorp/vault/latest/docs. |
Hi @pbchekin! I understand. I understand that my situation may not apply to other users. |
Hi!
I am using this configuration for an application.
And in the logs I see that it applies it generally correctly, but for some reason it ignores the
backend
setting and tries to connect using the default path (path: "/v1/secret/metadata/"
).The text was updated successfully, but these errors were encountered: