Pull-based deployment

As explained in Automating API Delivery

A pull-based deployment is a deployment model in which an agent in or near the target environment retrieves and applies desired configuration changes.

Pull-based deployment uses an agent in or near the target environment to retrieve and apply desired configuration changes. It is one of two GitOps deployment models, alongside push-based deployment. section 9.4.1

Git-tracked configuration gives deployment state an audit history and transaction log: reverting a configuration commit can roll the environment back, while the repository records how its state evolved. section 9.4.1

Use the model to frame these operational properties:

• Separate desired deployment state from the mechanism that applies it to the target environment. section 9.4.1
• Preserve deployment history in version control so teams can inspect, roll back, or roll forward configuration changes. section 9.4.1

Figure 9.7 GitOps pull-based deployment model

Use the deployment-model diagram to distinguish pull-based deployment from the push-based flow. section 9.4.1

How Automating API Delivery covers it

How deep it goes

Defines the model and relates it to version-control rollback, but does not detail agent reconciliation or configuration-fetch mechanics.

Examples

Uses a GitOps pull-based deployment model diagram and version-control reverts as concrete operational illustrations.

What it assumes

Assumes familiarity with GitOps, deployment configuration, version control, and target environments.

What you can do after

Evaluate deployment models and recognize how version control supports deployment auditing and rollback.

How it connects

Connects GitOps, push-based deployment, version control, configuration repositories, audit history, and rollback.

liveBookmanning.com

Read Automating API Delivery on liveBook Get the book at manning.com

Related concepts

• push-based deploymentcontrasts with · A push-based deployment is a deployment model in which a pipeline applies configuration changes to a target environment.
• GitOps operatorimplemented by · A GitOps operator is software that continuously reconciles a system’s runtime state with declarative configuration stored in a version-controlled source.
• GitOpshas part · GitOps is an operational approach that uses version-controlled declarative configuration as the source of truth and automation to apply or reconcile system state.

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.