I like this technology better because, you know, it promotes GitOps.
- Some person
For this reason it’s able to automatically and unattendedly detect configuration drift, and potentially revert them back to what is on its data source even if you haven’t touched the data source.
A CI pipeline that synchronizes configuration changes is not GitOps, and can’t automatically and unattendedly detect configuration drift unless it also periodically triggers a new build from master - which is not common.
Configuration Synchronization has always been a key aspect of Continuous Integration.
If you don’t need a control loop, you don’t need GitOps. If you don’t have a control loop, you are not doing GitOps, regardless of your desire to have it in your resumé.