Can't set collection_name on env_var or local configuration

[pedroceles]

From what I've seen in the codebase Invoke will only run certain configuration after tasks are loaded. This makes it inconvenient to have a project where invoke tasks live in other module than tasks.

That is because to find the tasks module I have to run inv -c [COLLECTION_NAME] [task_name]. When I simply want to run inv [task_name].

I could of course have a ~/.invoke.yaml that looks like this:

tasks:
  collection_name: "my_custom_tasks_module"

However this is impractical, since I'm working on a codebase where many people contribute, which the tasks module is already taken and I don't want to tell everyone to copy an invoke.yaml config file to their home directory. I'd like to make an invoke.yaml in my repo that would make invoke work customly "out of the box". In my opinion, Invoke should look for configuration files (invoke.(json|yml|yaml)) automatically and recursively in the parent directories before tasks are loaded.

I would be glad to try to hack something like that if it sounds good and no similar workarounds exists.

[dperetti]

So much this!!
And this tasks.py default name is so annoying. 😩

[CapedHero]

Moreover, tasks.py is ambiguous and may result in a conflict with other libraries that force using tasks.py...

[voidpp]

However this is impractical

You put it mildly, this is a very annoying bug...

[florisla]

I would not call this a bug since it's a deliberate design decision. Your code base is not compatible with the assumptions that invoke makes.

This is already configurable using the -c argument. If that is not convenient, configure your shell to map myinvoke to invoke -c mytasks.

[voidpp]

Well, since english is not my primary language maybe I misunderstand something but the documentation write this:

Both the sought collection name and the search root can be specified via configuration file options or as runtime CLI flags

If it is in the documentation and it's not working it's a bug...

[florisla]

Sorry, wasn't aware of that!

[jmcgill298]

Are there plans to resolve this issue?

[miso-belica]

Some more interesting thoughts about the issue can be found in #471 and #537