Feature Request: Git-Backed Triggers and Auto-Creation of Harness Entities from Git
S
Strange Kiwi
Summary
Support Harness triggers as git-backed entities, and let Harness automatically create and update entities from YAML stored in a repository’s .harness directory. Today, triggers cannot be stored in Git, so teams cannot manage their full Harness configuration as code alongside the service that uses it.
Problem
Our teams want to keep all Harness configuration for a service in that service’s repository, under .harness/. This includes pipelines, templates, input sets, and triggers, so the configuration is versioned, reviewed through pull requests, and deployed with the code it belongs to.
Pipelines and other entities can be managed this way, but triggers cannot, so this approach is blocked. Teams are left with a split setup: most configuration lives in Git, and triggers are created and maintained manually in the Harness UI or provisioned via IaCM.