That would open up so many possibilities!
Hypothetical example 1:
An Ignition file that could act as a computer inventory collector.
Boot up each of your computers one after one with the same USB stick.
Hardware information about each computer is collected and stored into the embedded Ignition file.
Hypothetical example 2: (A variation of the first example)
An Ignition file that could act as a Kubernetes cluster configurator and installer.
First boot up each of your computers as in the first example to collect hardware information.
After that the user would be able to enter a configuration mode where some choices need to be
made, with questions like “According to your available hardware, computer A would be suited to act as the kube-apiserver. Do you accept?”
The last mode would be an install mode where you need to boot up all the computers again.