Repository navigation
REQ 032
REQ-032: VIPM activation (Ubuntu-LabVIEW) is a deliberate, narrower automated exception to REQ-018, and is the only activation the complete-activation phase performs or needs (corrected 2026-11-07: real proof found no separate LabVIEW-activated precondition exists to document)
VIPM activation on the Ubuntu-LabVIEW family shall be performed non-interactively via vipm activate --direct-vipm-io, as part of the complete-activation phase's guest-side call chain, and is the only activation this phase performs or needs.
VIPM ships a documented, safe non-interactive activation flag that LabVIEW itself does not have an equivalent for; automating VIPM's activation specifically reduces operator burden without touching the human-only guarantee REQ-018 makes for LabVIEW, wherever such a human-only LabVIEW step genuinely exists. Real workflow_dispatch proof (#62, run 42394542555) confirms the Ubuntu-LabVIEW family has no separate LabVIEW-already-activated precondition to satisfy at all -- the former "documented operator convention" language was an unverified carry-over assumption from the Windows family, now corrected in complete-activation.sh's own usage text. The real call chain's lack of a LabVIEW-activation-state check was not a gap; there is no such state to check.
vm/ubuntu-labview/activate-vipm.sh runs VIPM_NONINTERACTIVE=1 vipm activate --direct-vipm-io --serial-number ... --name ... --email ... with no interactive prompt. It is invoked by vm/ubuntu-labview/capture-activation.sh (not directly by complete-activation.sh, which copies both scripts onto the guest and then invokes capture-activation.sh), unconditionally whenever a VIPM env file is supplied -- before capture-activation.sh's own LabVIEW-file-existence checks. A genuine activation-receipt.json (outcome: PASS) confirms VIPM reports a perpetual, Professional, validly-activated state and LabVIEW itself runs a real known-answer probe successfully with no LabVIEW-specific activation step ever having run.
Real workflow_dispatch dispatch of provision-ubuntu-vm.yml's complete-activation phase (#62, run 42394542555) against a disposable appliance, producing a genuine receipt with vipm.validThrough: "Perpetual", vipm.validActivationCode: true, and a passing LabVIEW known-answer probe -- not merely code review of the call chain, which this requirement's prior verification wrongly relied on alone.
Software-Requirements-Specification
High
Real workflow_dispatch of complete-activation (#62, run 42394542555) producing a genuine receipt with a perpetual, valid VIPM activation and a passing LabVIEW known-answer probe
vm/ubuntu-labview/activate-vipm.sh, vm/ubuntu-labview/capture-activation.sh, vm/ubuntu-labview/complete-activation.sh
Verified (live)