I
Indigo Mink
Currently, retrieving pipeline execution data via /pipeline/api/pipelines/execution/summary requires parsing deeply nested structures and inferring data like environment, main service, and artifact from varying stage types (e.g., MATRIX, Deployment). This introduces complexity for teams looking to build simple deployment observability or CI/CD metrics.
🔧 Proposed Feature
Introduce a simplified or higher-level endpoint that returns normalized execution-level summaries per pipeline. This could include:
  • pipelineIdentifier, planExecutionId
  • startTs, endTs, triggeredBy
  • Final status (Success, Failed, etc.)
  • environment
  • service (main deployed service)
  • artifact (deployed version or tag)
Benefits:
  • Greatly reduces the implementation burden for engineering teams building reporting/monitoring pipelines
  • Avoids reverse-engineering stage layouts and internal metadata
  • Encourages wider adoption of the Harness API for analytics and governance use cases
Thanks for considering, happy to provide more context if needed!