Skip to content
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

lakeFS configuration should load from a standard service location #2355

Closed
nopcoder opened this issue Aug 11, 2021 · 1 comment · Fixed by #2372
Closed

lakeFS configuration should load from a standard service location #2355

nopcoder opened this issue Aug 11, 2021 · 1 comment · Fixed by #2372
Assignees

Comments

@nopcoder
Copy link
Contributor

lakeFS configuration should first load from a known location. Common service location is machine level path: /etc/lakefs.yaml
Need to support the current home dot/hidden configuration and document the change in the integration documentation.

@nopcoder
Copy link
Contributor Author

lakeFS configuration lookup:

  1. ./config.yaml
  2. $HOME/lakefs/config.yaml
  3. /etc/lakefs/config.yaml

last one will be fallback to the current yaml- $HOME/.lakefs.yaml

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant