Skip to content

target globbing/grouping #23608

Description

@cburroughs

Is your feature request related to a problem? Please describe.

There are several different use cases that are tangentially related to grouping or globbing targets.

  • Sphinx or other documentation tools would want to run on "all the python code".
  • One off tricky non-inferable entry points (as an alternative to "write your own dep inference plugin")

A few more I can add:

  • Including all the python files in "big ML project" into one docker image. So one docker image may be able to run hundreds of different but related "ML flows". (These could each have their own image, but that would be a lot of images to juggle.)
  • Bundling libraries: For a vendor with a manged notebook environment there isn't an "executable" per se that needs to be deployed, but a bunch of python "libraries"that need to be statically identified (.py files, that need to show up on disk at the expected location)
  • Dynamic "registration:" I'll try to write this up in more detail but the basic idea is a tool for CI pipelines where where any folder can have some pipeline like my_pipline.py that defines a pipline, and a runner tool. The runner tool then has a glob dep like **/my_pipeline.py These are not exactly "entry points" since everything is only run through Pants, but the idea is that anyone can drop in pipeline file and it "just works".

Describe the solution you'd like

It feels like there is some sort of missing primitive here, but I'm not sure exactly what a non-plugin should look lik.e

Additional context

Slack threads:

Somewhat related:

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions