Fix eagle-exec deployment and simplify implementation (#5569)

- Remove sudo symlink creation (deploy user lacks passwordless sudo)
- Simplify eagle-exec to read from /opt/eagle0/.active-instance file
- Update deploy-blue-green.sh to write active instance to file
- Keep fallback to checking running containers if file doesn't exist

Users can add their own alias:
  alias eagle-exec='/opt/eagle0/scripts/eagle-exec.sh'

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>

.github/workflows/docker_build.yml

@@ -374,8 +374,6 @@ jobs:
           # Note: Auth is deployed separately via auth_build.yml - do NOT touch auth here
           chmod +x /opt/eagle0/scripts/*.sh
           [ -f "/opt/eagle0/scripts/bin/warmup" ] && chmod +x /opt/eagle0/scripts/bin/warmup
-          # Create eagle-exec alias (symlink in /usr/local/bin)
-          sudo ln -sf /opt/eagle0/scripts/eagle-exec.sh /usr/local/bin/eagle-exec
           GIT_SHA=\$(echo "\${EAGLE_IMAGE}" | sed 's/.*://')
           /opt/eagle0/scripts/deploy-blue-green.sh "\${GIT_SHA}"
 

scripts/deploy-blue-green.sh

@@ -35,6 +35,7 @@ WARMUP_SCRIPT="${SCRIPT_DIR}/warmup-eagle.sh"
 SAVES_DIR="${APP_DIR}/saves"
 FLUSH_MARKER="${SAVES_DIR}/.flush_complete"
 DEPLOYMENT_IN_PROGRESS="${SAVES_DIR}/.deployment_in_progress"
+ACTIVE_INSTANCE_FILE="${APP_DIR}/.active-instance"
 
 # Colors for output
 RED='\033[0;31m'
@@ -298,6 +299,10 @@ main() {
     create_flush_marker "${deploy_id}" "eagle-${staging}"
     log_info "[DEPLOY:${deploy_id}] Flush marker created - server will auto-invalidate stale cache"
 
+    # Write active instance file for eagle-exec helper
+    echo "eagle-${staging}" > "${ACTIVE_INSTANCE_FILE}"
+    log_info "[DEPLOY:${deploy_id}] Active instance file updated: eagle-${staging}"
+
     # Update .env for admin service
     local env_file="${APP_DIR}/.env"
     if [ "$staging" = "green" ]; then

scripts/eagle-exec.sh

@@ -1,43 +1,35 @@
 #!/bin/bash
 #
 # Helper to run docker exec against the active Eagle instance.
-# Automatically determines whether blue or green is active based on nginx config.
+# Reads the active instance from /opt/eagle0/.active-instance (set by deploy-blue-green.sh).
 #
 # Usage:
-#   ./scripts/eagle-exec.sh printenv GEMINI_API_KEY
-#   ./scripts/eagle-exec.sh jcmd 1 VM.flags
-#   ./scripts/eagle-exec.sh sh    # Get a shell
+#   eagle-exec printenv GEMINI_API_KEY
+#   eagle-exec jcmd 1 VM.flags
+#   eagle-exec sh    # Get a shell
 #
-# Or create an alias:
+# To create an alias, add to ~/.bashrc:
 #   alias eagle-exec='/opt/eagle0/scripts/eagle-exec.sh'
 #
 
 set -euo pipefail
 
 APP_DIR="${APP_DIR:-/opt/eagle0}"
+ACTIVE_FILE="${APP_DIR}/.active-instance"
 
-# Determine active instance from nginx config
-get_active_instance() {
-    local backend
-    backend=$(docker exec nginx grep -o 'eagle-[a-z]*:40032' /etc/nginx/nginx.conf 2>/dev/null | head -1 || echo "")
-
-    if [ "$backend" = "eagle-blue:40032" ]; then
-        echo "eagle-blue"
-    elif [ "$backend" = "eagle-green:40032" ]; then
-        echo "eagle-green"
+# Read active instance from file, with fallback
+if [ -f "$ACTIVE_FILE" ]; then
+    ACTIVE=$(cat "$ACTIVE_FILE")
+else
+    # Fallback: check which container is actually running
+    if docker inspect --format='{{.State.Running}}' eagle-blue 2>/dev/null | grep -q true; then
+        ACTIVE="eagle-blue"
+    elif docker inspect --format='{{.State.Running}}' eagle-green 2>/dev/null | grep -q true; then
+        ACTIVE="eagle-green"
     else
-        # Fallback: check which container is actually running
-        if docker inspect --format='{{.State.Running}}' eagle-blue 2>/dev/null | grep -q true; then
-            echo "eagle-blue"
-        elif docker inspect --format='{{.State.Running}}' eagle-green 2>/dev/null | grep -q true; then
-            echo "eagle-green"
-        else
-            echo ""
-        fi
+        ACTIVE=""
     fi
-}
-
-ACTIVE=$(get_active_instance)
+fi
 
 if [ -z "$ACTIVE" ]; then
     echo "Error: No active Eagle instance found" >&2