weft-firstboot

weft-firstboot

Pure-Go cloud-init-lite for openweft VMs.

One binary, one config file, four supported guest OSes. Runs once at the first boot of a freshly-installed VM to set hostname / create users / install SSH keys / drop files / run post-boot scripts, then writes a sentinel so subsequent boots short-circuit.

Status

V0.1 — initial release. Tested cross-build matrix : Linux + OpenBSD + FreeBSD + NetBSD on amd64 + arm64 (8 targets).

What it does

# /var/lib/weft-firstboot/user-data.hcl
hostname = "vmd-test"

user "openbsd" {
  ssh_authorized_keys = ["ssh-ed25519 AAAA... user@host"]
  groups              = ["operator"]
  doas                = true
  shell               = "/bin/ksh"
}

write_file "/etc/doas.conf" {
  content = "permit nopass keepenv :wheel\n"
  mode    = "0640"
  owner   = "root"
  group   = "wheel"
}

runcmd = [
  "rcctl enable ntpd",
  "rcctl start ntpd",
]

Apply :

weft-firstboot apply --config /var/lib/weft-firstboot/user-data.hcl

Or let the binary discover its user-data automatically — at first boot it probes :

1. --datasource <url> (explicit, highest priority)
2. NoCloud cidata disk : a block device with FS label cidata / CIDATA holding /user-data (+ optional /meta-data)
3. NoCloud-NET : http://<default-gateway>/user-data (typically http://10.0.2.2/user-data on QEMU SLIRP / http://192.168.x.1/user-data on vmnet)

Format autodetect : a #cloud-config magic header dispatches the cloud-config YAML legacy path ; anything else parses as HCL.

What it does NOT do

By design, V0.1 omits :

• Package install (apt, yum, pkg, pkg_add)
• Locale / NTP / keyboard / timezone modules
• Disk partition resize
• Datasources beyond NoCloud (no EC2/Azure/GCP/OpenStack/vSphere)
• Network configuration beyond DHCP

If you need any of these, file an issue — they're additive by design, not redesigns.

Config schema (HCL — preferred)

user "<name>" {} accepts :

• ssh_authorized_keys = ["<key>", ...]
• groups = ["<g>", ...]
• sudo = bool (Linux ; grants wheel)
• doas = bool (OpenBSD ; grants wheel)
• shell = "<path>" (default /bin/bash on Linux, /bin/ksh on OpenBSD, /bin/sh on FreeBSD/NetBSD)
• password_hash = "<crypt>" (empty → locked password, key-only)

write_file "<path>" {} accepts content, mode (octal, default 0644), owner, group (defaults root / root on Linux, root / wheel on the BSDs).

Config schema (cloud-config YAML — legacy)

Supported subset :

• hostname / fqdn
• users[].name, users[].ssh_authorized_keys, users[].groups, users[].sudo, users[].shell, users[].passwd
• write_files[].path, .content, .permissions, .owner
• runcmd[], bootcmd[] (string or [arg, arg, arg] form)

Everything else is silently ignored.

Idempotence

Every System primitive is idempotent. A second weft-firstboot apply against the same Config + same host is a no-op, not an error. This matters because :

• The sentinel may be lost (disk reset, VM image baked then re-cloned)
• An operator may manually re-run with --force for debugging
• Future runtime config reconciliation (planned) will share this apply path

CLI

weft-firstboot apply [flags]
  --datasource <url>     explicit datasource (skip auto-discovery)
  --config <path>        read user-data from this local file
  --sentinel <path>      applied-marker path (default /var/lib/weft-firstboot/applied)
  --force                re-apply even if sentinel is present
  --dry-run              parse config + print plan ; do not mutate
  -v, --verbose          log at debug level

weft-firstboot parse --config <path>
  Parse and print the normalised Config without applying.

weft-firstboot version
  Print version / commit / build date.

Building from source

go build ./cmd/weft-firstboot                    # host
GOOS=linux   GOARCH=arm64 go build ./cmd/...     # cross
GOOS=openbsd GOARCH=amd64 go build ./cmd/...
task cross-build                                  # all 8 targets to dist/

Pure-Go, CGO_ENABLED=0 is required (and tested in CI).

License

BSD 3-Clause — see LICENSE.