Define projects using patterns

[thompson-tomo]

Is your feature request related to a problem? Please describe.
In OpenTelemetry some of our contrib repos can contain a lot of projects and as such needing to list each project can lead to a bloated file and harder to mantain

Describe the solution you'd like
I want to be able use patterns in my project config to reduce my config and allow for easy scaling.

projects:
  - label: *
    changelog: src/*/CHANGELOG.md

In the above * represents the name of a folder and the value would be the label converted to lower-case with spaces replaced with underscores.

Describe alternatives you've considered
Dynamically generating the config using scripts.

Additional context
N/a

[miniscruff]

Hmm, I wonder if wrapping these in go templates would work. The issue would still be around converting a single element on yaml to many. Not sure yet.

[thompson-tomo]

What I was thinking was when determining the list of projects to process if a project contains a * it is removed from the list and in its place the resolved projects added.

[miniscruff]

What I was thinking was when determining the list of projects to process if a project contains a * it is removed from the list and in its place the resolved projects added.

Ah, just like a glob pattern, I see. I will think about this.

[miniscruff]

Ok more thoughts.

Glob is ok, it can return multiple matches but I guess that's fine. Assuming lower case and space replacements would be too much, but you could go template the key and name.

[thompson-tomo]

Correct, I would want the glob to return many matches. Agree the best solution would be templated name & key but also happy to auto generate ie lower case & replace spaces in keys. Perhaps that could be a default template if none specified.

[miniscruff]

#610 I think the v2 format expands ( or will ) the project config to be a bit more universal.