Currently, the pipeline execution history exposes a lot of set fields (e.g. env details, service for CD) that makes it easy for users to find which executions were tied to a specific env or service.

The ask is to expand this exposure so that custom attributes can be then searchable. Harness pipeline tags do not quite fit the use case as it is not possible to dynamically add a tag to an execution after the execution kicks off - the tag structure is too rigid to set this.

Use case 1:

In CI, I dynamically build a number of packages, which is determined programmatically, so it is not directly injectable as an input. One of my steps outputs the list of successfully/failed packages. I would like to "tag" my execution with this array of package names so that in the future, I can search the history and see some of the following metrics for which pipeline executions:

etc in a similar manner to how I can search deployments to "prod" today.