Harness enables a developer-centric experience for managing applications by implementing the GitOps methodology across its components. For example, you can trigger deployments in Harness using Git Pull and Push events. As a result, Harness GitOps integration allows you to use Git as the single source of truth when maintaining the state of the deployment process in Harness.
The following table describes the many GitOps-enabled components of Harness.
Links to Topics
Triggers with Git Webhooks
Use a Harness Trigger Git Webhook URL to execute a Harness deployment in response to a Github, BitBucket, or GitLab event.
File-based Repo Triggers
Initiate the Harness Trigger only when specific files in the repo are changed. For example, initiate the Trigger only when a Helm values.yaml file in Git is changed.
Using Git Push and Pull Request Variables in Harness Applications
Git push and pull request variables are available in a Trigger, and can be passed to the Workflows (and Pipelines) executed by the Trigger. An example variable is
Helm and Kubernetes Deployments