-
Notifications
You must be signed in to change notification settings - Fork 44
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
Fix/secrets management scripts, ssl for otp26 #1756
Conversation
@hauleth would be good if you could have a look at the makefile stuff in case i missed something. |
System.get_env("DB_SSL") == "true" && File.exists?("db-server-ca.pem") && | ||
File.exists?("db-client-ca.pem") && File.exists?("db-client-key.pem") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am pretty sure that checking for paths like that can fail in release, as these files may not be where we want them to be. Maybe instead use DB_SSL
as a path to where these files will be stored? That should make the configuration more flexible.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
agreed. yes we can update the certfile loading method for both db and grpc, can do this in a separate PR.
This PR fixes the secrets encryption/decryption scripts.
Behaviour is decoupled when running
make encrypt.*
andmake decrypt.*
to prevent overriding of local unencrypted/uncommited changes.This PR also adds in ecto ssl_opts, and also adds in the required staging/prod db ssl certs to get ssl properly supported on otp26.
I have also updated naming of the google cloud keys, so that it is easier to work with the makefile patterns.