Skip to content

core/onprem/vyos-template-import

Epoch: 2026E

Purpose

Register an already-existing Proxmox VyOS template into HyOps state as a compatibility path.

Why it exists

  • Some operators manage Proxmox template lifecycle outside HyOps.
  • The platform still needs a state-first contract for downstream VyOS edge modules.
  • This module provides a clean bridge without coupling to image seeding logic.

Required behaviour

  • MUST accept operator-supplied template_vm_id and template_name for an existing Proxmox template.
  • MUST publish at least:
  • template_key
  • template_vm_id
  • template_name
  • templates
  • MUST fail clearly if the referenced VMID is absent or not a template.
  • MUST NOT attempt image download, seed, or rebuild workflows.

Product boundary

  • This module owns state registration only.
  • It MUST NOT own routed edge policy or BGP/IPsec configuration.
  • It MAY be consumed directly by platform/onprem/vyos-edge when the default seed path is intentionally bypassed.