Configuration repository
A configuration repository is a typically version-controlled store containing configuration information that specifies how systems, applications, or deployment environments should be configured.
Automating API Delivery
An environment repository is a version-controlled repository containing the desired configuration for a deployment environment.
- How it is used
- Stores desired deployment configuration so application and API gateway changes can be reviewed, promoted, and deployed through Git.
- How deep it goes
- Walks through automated PRs, environment layouts, reconciliation, and operational drawbacks; defers solutions for centrally managed secrets.
- Examples
- Uses Dev, QA, Staging, and Production folders, automated configuration PRs, Kubernetes container-version manifests, and `git revert` rollbacks.
- What you can do after
- Operate/configure it by routing changes through reviewed PRs, promoting environment configuration, and reverting commits to roll back.
Read how Automating API Delivery explains configuration repository →
Platform Engineering on Kubernetes
A version-controlled repository containing the configuration that specifies which services and resources belong in a deployment environment.
- How it is used
- Organizes environment declarations so pipelines can deploy and promote services through Kubernetes environments.
- How deep it goes
- Compares YAML, Helm, and helmfile implementations, including duplication, release, and packaging trade-offs.
- Examples
- Uses kubectl apply, Helm dependencies, helmfile sync, pull requests, and Git repositories for environment promotion.
- What you can do after
- Operate environment deployments by declaring services in Git and selecting kubectl, Helm, or helmfile-based pipeline synchronization.
Read how Platform Engineering on Kubernetes explains configuration repository →
Related concepts
- GitOpsused by · GitOps is an operational approach that uses version-controlled declarative configuration as the source of truth and automation to apply or reconcile system state.
- repositoryalternative to · A software repository is an organized storage location or collection of project files and related artifacts, often managed with version history and change tracking.
- pull requestused by · A pull request is a version-control proposal to integrate changes from one branch or repository into another, typically supporting review and discussion before merging.
- configurationpart of · A specification of settings, parameters, or component relationships that determines how a system, application, model, or process is structured or operates.
- branchalternative to · A branch is an independently evolving line of development in a version-control repository, typically represented by a reference to a sequence of changes or commits.
- deployment pipelineused by · A sequence of automated or manual stages that builds, tests or validates, packages, and delivers software or models toward deployment.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.