liveBook · Manning

Push-based deployment

As explained in Automating API Delivery

A push-based deployment is a deployment model in which a pipeline applies configuration changes to a target environment.

Push-based deployment applies GitOps configuration changes from a deployment pipeline to a specified running environment. A commit triggers application-image construction and manifest generation; merging those manifests into the configuration repository triggers deployment. section 9.4.1

A typical workflow is:

  • Commit application code, triggering the deployment pipeline. section 9.4.1
  • Build the application container and generate deployment manifests from templates. section 9.4.1
  • Store generated manifests and API gateway configuration in the configuration repository. section 9.4.1
  • Merge changes to the mainline, causing the pipeline to apply the target state. section 9.4.1

Version control provides an audit history and transaction log: reverting a commit can roll back the environment, while earlier or later states can be redeployed. The model requires target-environment credentials in the CI/CD system, creating a security risk if that system is compromised. section 9.4.1 section 9.4.1

Figure 9.6 GitOps push-based deployments
figure

Trace the repository, pipeline, manifest, and running-environment flow. section 9.4.1

How Automating API Delivery covers it

How deep it goes
Traces commits, container builds, manifest generation, repository merges, deployment, rollback, and credential risk.
Examples
Uses application repositories, container images, manifest templates, API gateway configuration, commits, merges, and Git reverts.
What it assumes
Assumes application and configuration repositories, deployment-manifest templates, CI/CD automation, and target-environment access.
What you can do after
Operate a CI/CD pipeline that generates, versions, applies, and reverts configuration for a specified environment.
How it connects
Links GitOps, CI/CD, configuration repositories, deployment manifests, API gateways, and pull-based deployments.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Automating API Delivery. The section links point to the parts of the book it draws on.