Skip to content

[Feature]: Allow API Keys to be loaded from files, not just environment variables or directly in the config.yaml #9240

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

Open
bexelbie opened this issue Mar 14, 2025 · 0 comments · May be fixed by #9250
Labels
enhancement New feature or request

Comments

@bexelbie
Copy link
Contributor

bexelbie commented 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/

@bexelbie bexelbie added the enhancement New feature or request label Mar 14, 2025
@bexelbie 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
@bexelbie bexelbie linked a pull request Mar 14, 2025 that will close this issue
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant