GitOps with Database DevOps
Apply GitOps to database delivery using Harness, version schema changes, automate deployments, and ensure compliance via Git-driven workflows.
GitOps is an operational framework that brings DevOps best practices (version control, collaboration, compliance, and CI/CD) into the realm of infrastructure and database automation. In the context of Harness Database DevOps, GitOps enables teams to manage schema changes with the same rigor and scalability as application code. You can apply GitOps principles in several impactful ways:
Store configurations, database schemas, and migration scripts in Git repositories
Use pull requests and peer reviews to manage and approve changes
Trigger automated deployments through changes committed to Git
By integrating GitOps into your database lifecycle, you gain traceability, auditability, and reliable deployment workflows across all environments.
Implementation approaches
When adopting GitOps for database management, two primary branching strategies are commonly used:
Environment-by-Branch: Each environment (for example, dev, staging, prod) has a dedicated Git branch. Changes are promoted by merging from lower to higher environments. Go to Environment-by-branch development to learn how to configure this approach.
Trunk-Based Development: A single mainline branch (for example,
mainortrunk) is used, with pipelines or metadata controlling environment-specific behavior. Go to Trunk-based development to learn how to configure this approach.
Next steps
Go to Environment-by-branch development to set up branch-per-environment promotions.
Go to Trunk-based development to configure a single-branch pipeline strategy.
Go to Create a pipeline in Database DevOps to build your first GitOps-driven database pipeline.
Last updated
Was this helpful?