Skip to content

bootenv-customize

Should the machine use dynamic virtual media attached isos to boot

This param allows you to overlay dynamic customizations on top of BootEnvs. Its intended use is to reduce the number of bootenvs you have to create for what are ultimately trivial reasons. This Param is structured as a map of bootenv name -> override values. The override values have the same names and semantics of the equivalent fields in the OS section of the BootEnv, with the following exceptions:

  1. The Templates section is merged in with the Templates section from the BootEnv, with identically-named Templates from this Param overriding the ones from the BootEnv.

  2. You must use the per-arch SupportedArchitectures section to override kernel, initrd, iso, boot parameter, and boot loader values from the BootEnv.

You will get unexpected results if you create multiple overrides for the same BootEnv that have the same OS name but reference different ISOs, or have different kernel/initrd settings.

When overriding Sledgehammer, your bootenv-customize parameter should contain identical entries for the discovery and sledgehammer bootenvs. The discovery process assumes that a machine booted using discovery can transition to Sledgehammer without a reboot, and making discovery and sledgehammer use different kernels and initrds may lead to unexpected behaviour.