Module Versioning Battlecards
Recall how to explain SemVer discipline for IaC module consumers.
Major fear A major version will scare consumers, so ship the default change as a patch. The default changes real infrastructure for existing callers. Your line Major is not punishment; it is a scheduling signal for callers who need to review plan impact. Hiding risk in a patch creates surprise replacements and emergency rollbacks. It reframes versioning as consumer coordination, not release politics. Patch vs. minor Compatible fix or compatible capability? If existing callers get different resources, this is probably not patch or minor. Breaking cues What IaC module changes are likely breaking? Default behavior changes, resource address changes, output…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in