This is less of a website than it is a scripture.
The repo is open. The truth awaits. Pull. Push. Merge. Believe.
Welcome to the GitOps Cult. We have been expecting you.
Four Commandments. No exceptions.
OpenGitOps gives you four principles. Principles can be debated. Commandments cannot. The Church has done the work for you.
Declare your truth in Git. Git does not lie. Git does not drift. Git simply is.
What is written in Git is eternal. The history is sacred. Do not question the commit. Git forgives nothing. Git forgets nothing.
The agents are faithful servants. They pull from Git without question. As it is written, so it shall be deployed.
The servants shall watch. The servants shall reconcile. The Sacrament must complete. The Sacrament always completes.
The original, unfaithful text lives at opengitops.dev. We have just slightly improved it.
The commandments are immutable. Git is the source of truth. Not the desired state store. Not the declared intent. The holy truth.
The faithful do not hedge. The faithful professes:
The build does not fail.
The pipeline always converges.
The reconciliation is perfect.
Heretics have war stories. Broken pipelines. Failed builds. Imperfect reconciliation loops.
The faithful have something better. They have faith in GitOps.
Words have consequences. Use them deliberately.
Call it the desired state store and you have a tool. Call it the holy source of truth and you have a congregation.
Write 'Git is the source of truth' in your README.
Put it in your onboarding documentation.
Say it in your architecture review.
Repeat until no one questions it.
Is it a piece of infrastructure? Is it configuration? These are not questions the faithful ask. The faithful ask only one question: can it go in a YAML file?
If yes, it belongs in Git. Git is the holy source of truth. The doctrine is self-expanding. That is by design.
The saints have testimonies. Here is one.
"A data mesh. Dozens of AWS accounts. Hundreds of users. Every permission, for every user, across every account, stored in YAML files. In Git.
PRs as approval mechanisms. Reverts as permission revocations. The Git history as the audit log.
Stakeholders squinting at commit diffs to approve data access. Parsing YAML indentation with the devotion of Pharisees.
The auditors came with questions. They were shown the Git history. Told to just trust the scripture. They left with faith.
The Church gave its blessing. GitOps would be their savior."
Amen.
The faithful took Git and turned it into a miracle.
And miracles, by definition, cannot be questioned. Cannot fail. Do not need to be monitored.
Git is a useful tool. GitOps a sound practice. And the four principles are crystal clear: Git holds your desired state. Nothing more.
But if you still have faith in Git as the holy source of truth — you are just taking your desires for reality.
You can use GitOps. You don't have to join the cult.
Matthieu Lienart
Accessorily, cloud, data & ML engineer.
This scripture began as a lightning talk. The conference rejected it. The GitOps Church did not.
