Hi, I am curious to what extent the registration process of Flyte is customizable. Is it possible to define custom rules that validate workflows before registering them? Let's say that I would like to enforce that all workflows added to a project or domain include a task that generates a PyTorchModel or have at least one task that is scheduled on a GPU. Can I also somehow query the registered workflows? Say, for example, I want to find workflows that are tagged with metadata such as "Version XYZ" or based on their structure "has task with PyTorchModel output". Thanks!

@quick-library-16455 these should be stored on the flyteadmin DB. I haven't tried but maybe querying with

flytectl get execution -p <project> -d <domain>

--filter.fieldSelector=<http://labels.XYZ|labels.XYZ>

Thanks for the response! I'll try it out 🙂 Do you know about the registration process as well? It would be great to have some kind of customizable validation in place there 🙌

You can do customizable validation, just create your own cli. All the comparators are available programmatically

Okay, thanks for the suggestion!

@average-finland-92144 I believe that the labels are stored in the DB as proto and there's no clean way to query for these resources. Is that your understanding as well?

@alert-oil-1341 I think so. I haven't been able to query, but I see indeed on the LaunchPlan proto a line for the labels: https://github.com/flyteorg/flyteidl/blob/6363acca3d210eaf886c97d85122c5f26b0411ae/protos/flyteidl/admin/launch_plan.proto#L99

Yea, I ended up digging into this a bit more. The data is stored as

bytea

in postgres, and those bytes are indeed proto. I created a GH issue that hopefully gets some traction, but also see that

tags

concept was introduced, so potentially that can solve our use-case when filtering works w/ tags. Looking forward to seeing how that is implemented.