liveBook · Manning

Override

As explained in Effective Platform Engineering

A tool parameter override is a caller-supplied value that changes a shared pipeline's default arguments for a tool.

A tool parameter override is a caller-supplied value that changes a shared pipeline job’s default arguments for a tool or process. It preserves shared implementation while allowing project-specific behavior; without such flexibility, developers may abandon rigid shared jobs or request costly pull-request changes. section 6.3.7

Useful override patterns include:

  • Validate override values to preserve required guardrails, and permit tool or package version changes where practical. section 6.3.7
  • Use injection points for custom steps when changing arguments is insufficient; this separates parameter customization from inserting new pipeline behavior. section 6.3.7

Terraform plan job

A shared CircleCI job can accept a caller-provided terraform-init-additional-args or terraform-plan-additional-args value. The job still runs its standard initialization and planning commands, but each project can supply needed flags without modifying shared pipeline code.

How Effective Platform Engineering covers it

How deep it goes
Explains argument injection, validation guardrails, and Terraform command syntax, while stopping short of a complete validation implementation.
Examples
Uses Terraform init and plan additional arguments, variable-file settings, output paths, and optional post-checkout or post-plan steps.
What it assumes
Assumes familiarity with shared pipeline jobs, tool commands, and caller-provided parameters; teaches the customization pattern through Terraform examples.
What you can do after
Apply it via CircleCI job parameters to adapt shared Terraform commands without editing the shared job.
How it connects
Connects parameter overrides with reusable pipelines, shared jobs, custom step injection, version overrides, and parameter validation.

Also explained in

Compare how 5 books explain override →

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.