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
Add a new pattern to api_key in the config file to allow for file/ to denote that a file reference follows.
Motivation, pitch
This allows keys to be stored in temporary files that exist during startup or in secured locations and not in plaintext with the config or visible in the process tables/container inspection. This also allows for the config to be committed to git without concern or stored in a non-secured location.
This is similar to the existing os.environ and oidc prefixes.
Note: This issue was edited as I had missed how the environment variables were referenced as my initial use has been with placing hte keys directly into the configuration file.
bexelbie
changed the title
[Feature]: Allow API Keys to be loaded from files, not just environment variables or the config.yaml
[Feature]: Allow API Keys to be loaded from files, not just environment variables or directly in the config.yaml
Mar 14, 2025
The Feature
Add a new pattern to api_key in the config file to allow for file/ to denote that a file reference follows.
Motivation, pitch
This allows keys to be stored in temporary files that exist during startup or in secured locations and not in plaintext with the config or visible in the process tables/container inspection. This also allows for the config to be committed to git without concern or stored in a non-secured location.
This is similar to the existing os.environ and oidc prefixes.
Note: This issue was edited as I had missed how the environment variables were referenced as my initial use has been with placing hte keys directly into the configuration file.
Are you a ML Ops Team?
No
Twitter / LinkedIn details
https://www.linkedin.com/in/bexelbie/
The text was updated successfully, but these errors were encountered: