versionutils

Overview ¶

Package versionutils parses and compares Nutanix version strings.

Nutanix products report versions as '.'-separated integers: a plain release version such as "3.5.2.1" from AOS, or a Prism Central version such as "2024.3.1" or "pc.7.6.0.5". Parse a version once, then compare it as often as needed:

minPC := versionutils.Parse("7.6")
if versionutils.Parse(pcVersion).AtLeast(minPC) {
	// Prism Central is new enough.
}

Parse handles every Nutanix version format, so callers do not classify a version before parsing it. It normalizes away an optional "pc." prefix, surrounding whitespace and casing, and it knows that Prism Central moved from calendar versioning (202x.xx.xx) to a 7.x line, so a 7.x version is newer than any 202x.xx version despite comparing lower numerically. That rule is inert for AOS, which has no calendar-versioned releases.

Prism Element often truncates config.buildInfo.version (AOS 7.5.1 reports as "7.5") while fullVersion still carries the patch:

el8.5-release-ganges-7.5.1-stable-<commit>

Parse extracts the AOS token from that fullVersion form, ignoring a leading OS prefix (el8.5, ol9, …). When both fields are available, ParseReported combines them so a truncated short version is refined by fullVersion:

minAOS := versionutils.Parse("7.5.1")
if versionutils.ParseReported(short, full).AtLeast(minAOS) {
	// Prism Element is new enough.
}

Unparsable versions ¶

A version that is not '.'-separated integers, such as a development build reporting "master" or an empty string from a failed lookup, sorts as the newest possible version. A development build therefore satisfies every minimum-version gate, which is deliberate: preflight-style checks should not block a test or debug cluster.

A caller that has no version at all is asking a different question, and answers it before parsing:

if pcVersion == "" {
	return false // nothing was reported, use the fallback path
}
return versionutils.Parse(pcVersion).AtLeast(minPC)