Blueforce-Linux/tests/check-configs.sh
emirhanmamak-blueforce ef102b9657 feat(field-os): provisioning layer, real ISO build, offline contracts
Adds the Blueforce Field OS provisioning stack on top of the existing fleet
architecture, without rewriting the working systems (installer, diagnostics,
Ansible, WireGuard/SSH/xRDP/RustDesk, Docker policies, monitoring, Docusaurus).

ISO build (the previous builder was a skeleton that produced no medium):
- boot layout is read from the base ISO at build time via
  `xorriso -report_el_torito as_mkisofs` and rebuilt with `-as mkisofs`;
  `-boot_image any replay` cannot work on Ubuntu live ISOs because the GRUB2
  MBR lives in the source image's first 16 sectors and the EFI system partition
  is an appended partition, neither of which is a file in the ISO9660 tree
- preflight now asserts El Torito boot metadata positively: xorriso exits 0 on
  a non-ISO input, which previously let an arbitrary file pass --check
- artifact produced and verified: dist/Blueforce-Field-OS-1.0.0-amd64.iso,
  6 481 917 952 bytes, SHA256 cb0cc56f...d431296, BIOS+UEFI entries preserved,
  /autoinstall.yaml at the media root, casper/minimal.squashfs byte-identical
  to the base
- recorded baseline deviation: the verified medium on the build host is the
  Desktop flavour, so the manifest carries a baseline_deviation block instead
  of hiding it; Server remains one flag away

Offline and identity:
- offline APT contract with concrete package requirements, pin format and an
  audit table; builds fail closed while pins are UNPINNED
- autoinstall keeps interactive-sections: [storage]: the operator confirms the
  target disk, and no automatic wipe is ever performed
- firstboot terminal wizard for the 8-digit dealer id, three-state lifecycle
  (PROVISIONED_OFFLINE -> ENROLLED -> READY) with fail-closed gates, so a
  missing internet link or WireGuard handshake cannot fail provisioning but can
  never produce a false READY

Fleet and migration:
- five read-only Ansible playbooks for Field OS version, provisioning,
  enrollment, remote channels and offline readiness, all wave-scoped with a
  separate production override
- Windows pre-migration inventory and data export extended to the full brief
  scope, read-only, never collecting credentials

Tests: tests/run-all.sh -> 8/8 pass, exit 0. Boot acceptance (UEFI, Legacy
BIOS, Secure Boot), air-gapped install, real enrollment endpoint and Windows
rollback remain LAB work and are listed in IMPLEMENTATION-REPORT.md.
2026-09-16 11:14:42 +03:00

74 lines
3.5 KiB
Bash
Executable file

#!/usr/bin/env bash
# Parse fleet configuration and validate executable shell scripts without running them.
set -euo pipefail
REPO_ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
FAIL=0
fail() { printf 'FAIL: %s\n' "$*" >&2; FAIL=1; }
pass() { printf 'OK: %s\n' "$*"; }
# Every Bash script under scripts/ must pass syntax parsing. Non-Bash assets are ignored.
while IFS= read -r -d '' script; do
if head -n 1 "$script" | grep -qE '^#!/usr/bin/env bash|^#!/bin/bash'; then
bash -n "$script" && pass "bash parses: ${script#$REPO_ROOT/}" || fail "bash parse error: ${script#$REPO_ROOT/}"
fi
done < <(find "$REPO_ROOT/scripts" -type f -print0)
# All Ansible and deployable configuration YAML must parse through PyYAML safe_load.
while IFS= read -r -d '' yaml_file; do
if python3 - "$yaml_file" <<'PY'
import sys
import yaml
with open(sys.argv[1], encoding='utf-8') as handle:
yaml.safe_load(handle)
PY
then
pass "yaml parses: ${yaml_file#$REPO_ROOT/}"
else
fail "yaml parse error: ${yaml_file#$REPO_ROOT/}"
fi
done < <(find "$REPO_ROOT/ansible" "$REPO_ROOT/config" "$REPO_ROOT/monitoring" -type f \( -name '*.yml' -o -name '*.yaml' \) -print0)
# JSON configuration must parse as JSON, not merely as JavaScript.
while IFS= read -r -d '' json_file; do
if python3 - "$json_file" <<'PY'
import json
import sys
with open(sys.argv[1], encoding='utf-8') as handle:
json.load(handle)
PY
then
pass "json parses: ${json_file#$REPO_ROOT/}"
else
fail "json parse error: ${json_file#$REPO_ROOT/}"
fi
done < <(find "$REPO_ROOT/config" "$REPO_ROOT/monitoring" -type f -name '*.json' -print0)
# Required values preserve the naming and wave policy in docs/09 and docs/10.
INV="$REPO_ROOT/ansible/inventory/hosts.example.yml"
GV="$REPO_ROOT/ansible/inventory/group_vars/all.yml"
[[ -f "$INV" ]] || fail "missing inventory example: $INV"
[[ -f "$GV" ]] || fail "missing shared group variables: $GV"
for group in lab pilot_1 pilot_2 wave_1 wave_2 production; do
grep -q "^[[:space:]]*$group:" "$INV" || fail "inventory missing wave group: $group"
done
for key in wg_subnet wg_interface monitoring_endpoint meg_image_tag reboot_grace_seconds support_bundle_dir; do
grep -q "^$key:" "$GV" || fail "group_vars/all.yml missing key: $key"
done
for pb in bf-collect-logs.yml bf-gui-on.yml bf-gui-off.yml bf-run-script.yml; do
grep -q '^ hosts: "{{ operation_wave' "$REPO_ROOT/ansible/playbooks/$pb" || fail "$pb must dynamically target operation_wave"
grep -q 'production_override: false' "$REPO_ROOT/ansible/playbooks/$pb" || fail "$pb must default production_override to false"
done
FIREWALL_POLICY="$REPO_ROOT/config/firewall/blueforce-docker-user-restore.sh"
bash -n "$FIREWALL_POLICY" && pass 'bash parses: config/firewall/blueforce-docker-user-restore.sh' || fail 'bash parse error: config/firewall/blueforce-docker-user-restore.sh'
grep -q '^After=docker.service$' "$REPO_ROOT/config/systemd/blueforce-docker-firewall.service" || fail 'Docker firewall service must wait for Docker'
grep -q '^Wants=blueforce-docker-firewall.service$' "$REPO_ROOT/config/systemd/docker.service.d/blueforce-docker-firewall.conf" || fail 'Docker drop-in must start firewall policy'
if grep -RniE --include='*.yml' --include='*.yaml' --include='*.json' '^[[:space:]]*[^#].*(image:[^#]*:latest([[:space:]#]|$)|watchtower)' "$REPO_ROOT/ansible" "$REPO_ROOT/config" "$REPO_ROOT/monitoring"; then
fail "forbidden moving tag or Watchtower configuration found"
fi
if [[ "$FAIL" -ne 0 ]]; then
printf 'check-configs: FAILED\n' >&2
exit 1
fi
printf 'check-configs: all passed\n'