-
Notifications
You must be signed in to change notification settings - Fork 17
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
Add an ability to manage lock files in nested directories #464
Comments
Low priority as of now. |
Important for: aicoe-aiops/project-template#25 it would be useful for: https://github.com/thoth-station/jupyter-nbrequirements/pull/282/files |
What if different steps in a pipeline requires use of different hardware (just to mention one degree of freedom for the selection of the software stack)? each software stack should be coupled with a specific .thoth.yaml. See links above. |
Adviser's input require direct dependencies, runtime environment and other vectors being constant. The resolved stack is specific to the input vector provided. |
This can be closed as we introduced overlays. The overlay approach taken can manage multiple lock files for different runtime environments. See overlays configuration option. |
Is your feature request related to a problem? Please describe.
Some projects maintain lock files not in a git root directory, but in some of the nested dirs present in the repo. This structure makes it harder to integrate with Thoth.
Describe the solution you'd like
Add an ability to maintain lock files in nested directories. The configuration file .thoth.yaml will be picked from one of the parent directories.
Describe alternatives you've considered
Copy .thoth.yaml file into nested directories so that the configuration is picked along with the lock file.
The text was updated successfully, but these errors were encountered: