From 43f09f76bc1b749d25c9222f57236d0fec2b2549 Mon Sep 17 00:00:00 2001
From: zenaku <zenaku@simplifiedprivacy.org>
Date: Mon, 21 Sep 2026 15:25:04 +0200
Subject: [PATCH] feat: inject legacy API token during migration

---
 02-migrate-peers.sh | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/02-migrate-peers.sh b/02-migrate-peers.sh
index 14fe20e..2597874 100644
--- a/02-migrate-peers.sh
+++ b/02-migrate-peers.sh
@@ -142,6 +142,15 @@ echo "$LEGACY_PRIVATE_KEY" > "$WG_SERVER_KEY"
 echo "$LEGACY_PUBLIC_KEY"  > "$WG_SERVER_PUB"
 ok "Private key written to server keyfile."
 
+# ─── INJECT API TOKEN ────────────────────────────────────────────────────────
+sep
+info "Injecting legacy API token..."
+LEGACY_API_TOKEN=$(grep -E '^API_TOKEN=' "$BACKUP_DIR/legacy.env" | cut -d= -f2 | tr -d '[:space:]')
+[ -z "$LEGACY_API_TOKEN" ] && warn "No legacy API token found, keeping generated one." || {
+    sed -i "s|^OPERATOR_API_TOKEN=.*|OPERATOR_API_TOKEN=$LEGACY_API_TOKEN|" "$OPERATOR_DIR/.env"
+    ok "API token injected from legacy."
+}
+
 # ─── START NEW WIREGUARD ──────────────────────────────────────────────────────
 sep
 info "Starting new WireGuard with legacy identity..."