Autoinstall from a cidata drive instead of the configurator
Look for a drive labeled cidata at startup. If it carries the configurator's own output files, copy them into /root and skip the wizard -- everything downstream then runs the ordinary path against ordinary inputs. No drive, no change. The required pair matches what the orchestrator treats as mandatory, so a drive with less than that falls back to the wizard rather than failing the boot. Claude-Session: https://claude.ai/code/session_01Sy3HeoBqb13ahLuaiP2UkM
This commit is contained in:
1 parent
f5aa88b06c
commit
a4ec97d174
2 files changed
+41
-2
No files matched your search
@@ -16,6 +16,7 @@ while [[ $# -gt 0 ]]; do
|
||||
--full-name-file) export OMARCHY_INSTALL_FULL_NAME_FILE="$2"; shift 2 ;;
|
||||
--email-file) export OMARCHY_INSTALL_EMAIL_FILE="$2"; shift 2 ;;
|
||||
--encrypt-file) export OMARCHY_INSTALL_ENCRYPT_FILE="$2"; shift 2 ;;
|
||||
--ssh-keys-file) export OMARCHY_INSTALL_SSH_KEYS_FILE="$2"; shift 2 ;;
|
||||
*) echo "omarchy-iso-install: unknown arg $1" >&2; exit 2 ;;
|
||||
esac
|
||||
done
|
||||
|
||||
Reference in new issue
Block a user