-
Notifications
You must be signed in to change notification settings - Fork 375
Allow configuring loader root, collection, etc values #310
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
Comments
So basically this feature would allow someone to run an invoke script on a server without having to make external systems cognizant of where the script is located -- +1 :) |
There are some extra thoughts and info in #291, make sure that is considered before we work on this. |
And there's also another request in #455, which prompted me to rethink things a bit (now that we're 2 years of new features into the codebase...) The currently-functional "best" workaround for the problem of "I want to default to loading something other than Arguably this is even more easily served by requesting users to just add That said, there may be another option too. I don't recall off the top of my head if it's feasible (small chance it even "just works" right now, actually!) but we might be able to ensure basic config bits are loaded/honored before collections are. Then your tasks:
collection: invfile (That's not the real config setting; I don't think it actually exists yet, at least not publicly.) There's a bit of chicken and egg here (part of the config system includes data loaded from the task collection!) but that's already a semi-solved problem (for other reasons) so it probably just means additional tweaks to the |
+1 for last option from @bitprophet above if possible |
Been doing this + #329 at the same time as the core need is the same (Config handy earlier in process and in more parts of the system). Most notes-to-self have been over there. FYI. |
This is in! and will be released momentarily in v0.20. Changelog says all, tl;dr should be able to set |
I.e. users should be able to configure how task collections are loaded, from global or per-user config files, and have those serve as the defaults for
--root
,--collection
etc.This way users can easily set up a default set of tasks for
invoke
if they're not in a folder or tree containing atasks.py
.It's possible this will require improving the loader process itself so there's a concept of default + override, since otherwise, anybody setting this kind of 'default tasks location' value might find it 'blocking' the current load behavior unintentionally. But hopefully we can simply leverage the regular ol' configuration hierarchy for this?
The text was updated successfully, but these errors were encountered: