liveBook · Manning

Pipeline injection point

As explained in Effective Platform Engineering

A pipeline injection point is a defined location where callers can supply additional custom pipeline steps.

A pipeline injection point is a defined location where callers supply additional custom steps without changing shared pipeline code. It preserves reusable defaults while allowing local workflow needs. section 6.3.7

Implement injection points by:

  • Combining injection points with validated parameter and tool-version overrides so customization retains guardrails. section 6.3.7

Terraform plan customization

A shared Terraform plan job can accept an after-checkout step that computes a varfile at runtime. The caller adds that command without modifying the shared job or waiting for a shared-code change. section 6.3.7

How Effective Platform Engineering covers it

How deep it goes
Defines typed step parameters, lifecycle placement, and execution syntax, while stopping short of broader pipeline design.
Examples
Uses CircleCI job parameters and a Terraform plan job with after-checkout, after-init, after-plan, and after-complete steps.
What it assumes
Assumes familiarity with shared jobs, pipeline parameters, CircleCI configuration, and Terraform commands.
What you can do after
Build reusable CircleCI jobs that callers customize at defined lifecycle points without editing shared implementations.
How it connects
Connects shared pipeline code with parameter overrides, versioning, and guardrails.

Related concepts

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