Load project level configuration files earlier

Open
#961 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
cli

Research direction

Start by tracing how invoke.yaml is discovered and how the tasks directory is loaded when execution begins. Check how search_root is applied to the tools/ layout, then verify that a root-level configuration can be read before task discovery and that the existing layout still works.

Written by the indexing model from the issue text.

Description

We've moved most of our codebase to a mono repo and have moved our tasks directory to a subdirectory.

Our project-structure looks like this:

  • tools/
    • tasks/init.py
    • ...
  • invoke.yaml

We were hoping to use the invoke.yaml at project root with the search_root setting set to the subdirectory "tools".

Sadly this is not possible since the tasks directory must be persent at the directory of invoke execution.

Can this somehow be changed, so that the project level configuration file is loaded, before invoke is trying to load the tasks.py/tasks directory?

Dominant language
Python
Stars
4.8k
Forks
412
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pyinvoke/invoke

All issues in pyinvoke/invoke

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.