liveBook · Manning

Tool version override

As explained in Effective Platform Engineering

A tool version override is a caller-supplied version selection that replaces a shared pipeline's default tool or package version.

A tool version override lets a developer replace a shared pipeline’s default tool or package version with a newer or older one. section 6.3.7

Use the override when shared pipeline dependencies create friction:

  • Select a newer version when an orb has not yet provided a minor or patch update. section 6.3.7
  • Select an older version when a newly released orb updates tools or packages but breaks a small subset of users. section 6.3.7
  • Keep teams moving without requiring a pull request or waiting for the orb maintainer to change shared code. section 6.3.7

Orb update compatibility

A team using the current orb encounters a breaking package update. It overrides the package version to the previous release while the shared orb evolves. section 6.3.7

How Effective Platform Engineering covers it

How deep it goes
Explains the operational rationale and expected effect, but does not specify an override parameter or configuration syntax.
Examples
Uses delayed minor or patch updates and breaking orb releases as the central compatibility examples.
What it assumes
Assumes familiarity with shared pipeline libraries and orbs; does not teach pipeline construction or version-selection syntax.
What you can do after
Apply it through a shared pipeline to choose a compatible newer or older tool version without modifying the shared orb.
How it connects
Connects shared pipeline libraries with orbs, tool versions, package updates, and maintainer-controlled changes.
Cover of Effective Platform Engineering
liveBookmanning.com
Read Effective Platform Engineering on liveBook Get the book at manning.com

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.