A configuration state file is a version-controlled, declarative file that declares the desired configuration state of a managed API system. In an APIOps workflow, changing this file is the mechanism for changing configuration. section 9.4.1
A GitOps-managed configuration state file supports:
- Immutable, versioned declarations with history, access controls, auditing, pull requests, and CODEOWNERS. section 9.4.1
- Automated agents or deployment pipelines that pull the declared state. section 9.4.1
- Continuous reconciliation of actual system state with desired state, including detection and correction of drift. section 9.4.1
- A controlled alternative to manual API gateway UI changes, which may be error-prone and lack equivalent audit history. section 9.4.1
Figure 9.6 GitOps push-based deployments
Compare the push-based deployment model with the pull-based model to understand how declared configuration reaches the managed system. section 9.4.1
