Wildcard-include tasks from a dir

[pentago]

I was thinking about a possibility of having a directory full of individual task files and just including the entire directory of tasks without having to specify all of them one by one.

This way, one would be able to make compositions from predefined tasks suitable for a need.
For example, in large teams working on various projects, one person might have different needs than the other (e.g. OS or tooling-wise).

My proposal is mostly aimed at working in an environment with multiple people to be able to share tasks.

For example, consider this definition:

version: '3'

includes_dir:
  - dir: tasks/*
  - dir: os/mac/*

tasks:
  setup-mac-infra:
    cmds:
      - task: setup-cluster
      - task: setup-metrics-server
      - task: setup-cilium
      - task: setup-coredns
      - task: setup-cert-manager
      - task: setup-gateway-api
      - task: setup-workload
      - task: setup-netpols
      - task: run-hubble

  mac-cleanup:
    cmds:
      - task: cleanup

Or something along those lines - just being able to include all (we have hundreds) of tasks and be able to share across the teams.

Thoughts?

[kwhtsng]

Do you have any updates on this issue?

[trulede]

@kwhtsng @pentago I would suggest to create a PR that uses the existing schema with the following:

1. Glob the include path and identify include files.
2. For each include file, synthesise an import namespace based on the path (foo/bar/Taskfile.yml has namespace foo:bar).
3. Include the file.
4. Consider if any of the existing imports schema fields are applicable (I suspect most are not).

This will likely be a bit limited in operation, but that may be OK.

Alternative is to write a task that rewrites the include section of a taskfile, in which case you can keep control of the mechanism. For example, I programmatically generate taskfiles that have versioned includes.