T
Travis Gosselin
It would be helpful to include some type of interface, perhaps JQ expression, for consumers to filter a catalog view based on a complex object JSON field. This is possible in creating new catalogs with filter expressions for Admins, but not for consumers who wish to filter by the object.
There are two scenarios below to help indicate benefit:
  1. We have our CI/CD pipelines stored as objects that enable us to detect what types of things people are doing in their pipelines, using certain actions/tasks, using base workflows, etc. We pull out some of this into calculated fields. We need to search adhoc by some additional actions/tasks, and other than a developer manually going through all the pipelines (3000) in source control, they could easily query with jq the definitions and filter to pipelines using some of the feature they are thinking about making breaking contract changes too (many use cases on why you'd want to identify impact to pipelines).
  2. Similar scenario with objects in the API space, where we can identify API specs (Stored as OpenAPI) using certain models, notation or constructs and filter it down.