I'm facing some issues with regards to using a configuration file and I'm not sure whether it's a bug in the code or the docs are confusing.
What I want to do is to have my tasks in a different directory e.g. ops, instead of tasks. If I read the docs correctly, that should be possible by placing a invoke.yaml file in the project's root. It appears that doesn't work:
The above shows the per-project configuration file is loaded late, perhaps after the tasks discovery. But then I wonder if the tasks.collection_name can actually be specified per-project.
Hello,
I'm facing some issues with regards to using a configuration file and I'm not sure whether it's a bug in the code or the docs are confusing.
What I want to do is to have my tasks in a different directory e.g.
ops
, instead oftasks
. If I read the docs correctly, that should be possible by placing ainvoke.yaml
file in the project's root. It appears that doesn't work:Calling the task results in an error:
Unless I explicitly pass the
-c
flagThe above shows the per-project configuration file is loaded late, perhaps after the tasks discovery. But then I wonder if the
tasks.collection_name
can actually be specified per-project.FWIW: