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
Hello PB team,
Quick suggestion.
I think it would be much nicer if you could pass the secret upon initializing the library or make it an env variable.
Motivations:
Dealing with updating config file secrets in a Dockerfile after loading a vault like Hashicorp or dotenv is clunky
Variable leaks into the the docker image config file
You cannot commit the config file with the secret. You would have to commit an example config file to avoid devs accidentally comitting the secret. One more thing people have to configure etc.
The text was updated successfully, but these errors were encountered:
Hello PB team,
Quick suggestion.
I think it would be much nicer if you could pass the secret upon initializing the library or make it an env variable.
Motivations:
The text was updated successfully, but these errors were encountered: