-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Change config to yaml #51
Labels
kind/feature
New feature or request
Comments
I think it's worth doing. Easier to work with, and easier to read. Why would we have some keys nested and some flattened? Why not all nested like:
instead of
|
yeah, that works too. |
yaml sounds good to me |
dmartinol
pushed a commit
to dmartinol/feast
that referenced
this issue
Jul 25, 2024
…missions Fix auth tests with permissions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Configuration for feast is currently done using environment variables only. As the number of parameters grows in size, this method of configuring the deployment becomes increasingly unwieldy.
Describe the solution you'd like
We want to move away from KVs, which are limited when it comes to nested config, eg. for job options. Currently we set it as a json string.
Describe alternatives you've considered
If we use yaml, it would potentially look something like this:
We can still continue to support env vars for overriding config.
The text was updated successfully, but these errors were encountered: