Skip to content

v9.8.0 Controlled Source VM Clone

Latest

Choose a tag to compare

v9.8.0-controlled-source-vm-clone

v9.8.0-controlled-source-vm-clone adds a lab-only controlled clone path for environments where Prism exposes a golden VM but no Image Service disk image.

Highlights

  • Platform Admins can approve discovered VM inventory records as bounded source VM clone candidates.
  • Controlled AHV lifecycle selection now supports either an approved image or an approved source VM.
  • Prism Central connection tests now discover VMs as read-only inventory.
  • Lab configuration accepts NDC_AHV_ALLOWED_SOURCE_VM_UUID or NDC_AHV_PE_ALLOWED_SOURCE_VM_UUID as an alternative to image UUIDs.
  • Clone submission uses explicit Prism clone endpoints and records source-VM evidence in the lifecycle event ledger.
  • Dedicated smoke:ahv-source-vm-clone command validates the approved-source-VM path without falling back to Image Service create.

Safety Boundary

  • Source VM clone remains disabled unless APP_ENV=lab, real AHV adapter, controlled provisioning, lifecycle switches, approved NDC scope, lifecycle proof, and authorization envelope are all present.
  • The selected source VM must be approved in NDC and must match the private allowed source VM UUID.
  • No credential material is persisted in inventory records, audit metadata, frontend state, docs, or exported evidence.

Suggested Checks

npm run validate:ahv-lab-config
npm run smoke:ahv-source-vm-clone -- -BaseUrl http://127.0.0.1:18080 -EnvironmentName ndc-lab-source-clone-01
npm run test -- server/ahvLabRuntime.test.ts server/apiServer.test.ts src/services/cloudStudioApi.test.ts
npm run build