-
Notifications
You must be signed in to change notification settings - Fork 4
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
Figure out how to have less dependency on Vault. #88
Comments
I wonder if we can do something like this:
We could then add to our
Meanwhile anyone else using it could point it to a config file with secrets in it they store elsewhere or they could just not set it at all and find another way to inject the secrets ( I'm also not sure if |
I think slapping a variable on it is definitely the correct start, I like it! |
This lets you run prod with a local postgres instance. We prolly need to document the vault stuff, but I think that's better suited for #88 to handle. I *think* this MR is ready to rock, it's deployed and working on `scram-pentest.ocean.cu-es.net` presently.
Right now, we have a lot of dependency on vault for rendering secrets. We should consider how to make that not mandatory.
The text was updated successfully, but these errors were encountered: