Semantic versioning

Q: How deeply does Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform cover semantic versioning?

Defines major, minor, and patch changes, then stops short of a full specification of semantic-versioning approaches.

As explained in Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform

Semantic versioning is a version-numbering scheme in which major, minor, and patch components communicate the kinds of changes between releases.

Semantic versioning assigns major, minor, and patch numbers that communicate the significance of configuration changes between module releases. section 5.2

Apply the version components consistently:

Increment the major version for significant changes that remove inputs, outputs, or resources. section 5.2
Increment the minor version for configuration, input, or output changes that do not affect dependencies using earlier versions. section 5.2
Increment the patch version for minor configuration-value changes limited to the module and its resources. section 5.2

Database module migration

A database module changes from v1.0.0 to v2.0.0 after removing its password output and exposing a secrets-manager path instead. Downstream infrastructure must retrieve the password before creating the database. section 5.2

$ git log --oneline
7157d3e (HEAD -> main, tag: v2.0.0, origin/main) 
➥Change database module to store password in secrets manager
5c5fd65 (tag: v1.0.0) Add database factory module

A Git history makes releases auditable by showing the commits associated with v1.0.0 and v2.0.0. section 5.2

How Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform covers it

Cover of Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform

liveBook manning.com

Read Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Building Web APIs with ASP.NET CoreSemantic versioning is a version-numbering convention using MAJOR, MINOR, and PATCH components whose increments communicate compatibility and change significance.
liveBook manning.com

Go in Action, Second EditionSemantic versioning is a versioning convention in which changes to major, minor, and patch components communicate compatibility and release significance.
liveBook manning.com

API Design PatternsA semantic version string is a dotted three-number representation whose major, minor, and patch components communicate the nature of software changes.
liveBook manning.com

The Design of Web APIs, Second EditionA semantic version number is a version identifier with major, minor, and patch components whose changes conventionally communicate compatibility impact.
liveBook manning.com

The Art of CodeSemantic versioning is a version-numbering convention in which major, minor, and patch components communicate compatibility and change significance.
liveBook manning.com

GitHub Actions in Action: Continuous integration and delivery for DevOpsSemantic versioning is a versioning scheme that communicates compatibility and change significance through major, minor, and patch version numbers.
liveBook manning.com

Terraform in Depth: Infrastructure as Code with Terraform and OpenTofuA semantic version is a version identifier following major, minor, and patch precedence rules.

Compare how 8 books explain semantic versioning →

Related concepts

major versionhas part · A major version is the primary component of a version identifier that distinguishes a release line and commonly signals potentially backward-incompatible changes.
FluentBitused by · Fluent Bit is a lightweight, open-source telemetry agent for collecting, processing, enriching, and forwarding logs and other event data.

This explainer was generated by Manning's knowledge graph from the text of Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform. The section links point to the parts of the book it draws on.