-
-
Notifications
You must be signed in to change notification settings - Fork 94
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
Rename *-paths to *-dirs options #1287
Conversation
The `*-paths` option in our `vast.yaml` feel really confusing. A directory is necessarily a path, but not the other way round. The old options continue to work, but are deprecated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not much to say, tested and observed the behavior that I commented on below.
Co-authored-by: Matthias Vallentin <matthias@tenzir.com>
It was only introduced after the most recent release, so it does not need to stay in marked as deprecated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems to work as intended. It even prints the warning twice for emphasis 😛 .
Noticed that as well, we seem to read the schemas twice on startup. I'll write a story so we don't forget about that. |
📔 Description
The
*-paths
option in ourvast.yaml
feel really confusing. A directory is necessarily a path, but not the other way round.The old options continue to work, but are deprecated.
📝 Checklist
🎯 Review Instructions
Try it out locally.