From 7a24ff6702b50b3761df6c8b625cd1b9f0e03465 Mon Sep 17 00:00:00 2001
From: Viktor Barzin <viktorbarzin@meta.com>
Date: Wed, 18 Mar 2026 00:04:51 +0000
Subject: [PATCH] =?UTF-8?q?fix(provision):=20use=20$USERNAME/$EMAIL=20dire?=
 =?UTF-8?q?ctly=20=E2=80=94=20Woodpecker=203.x=20env=20vars?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Woodpecker 3.x exposes pipeline variables with their original key names
(USERNAME, EMAIL), not CI_PIPELINE_VARIABLE_ prefix.
---
 .woodpecker/provision-user.yml | 8 +-------
 1 file changed, 1 insertion(+), 7 deletions(-)

diff --git a/.woodpecker/provision-user.yml b/.woodpecker/provision-user.yml
index 61a49a1f..f0a25520 100644
--- a/.woodpecker/provision-user.yml
+++ b/.woodpecker/provision-user.yml
@@ -12,16 +12,10 @@ steps:
   - name: validate-inputs
     image: alpine
     commands:
-      - env | grep -i "CI_\|USERNAME\|EMAIL\|PROVISION" | sort || true
       - |
-        USERNAME="$CI_PIPELINE_VARIABLE_USERNAME"
-        EMAIL="$CI_PIPELINE_VARIABLE_EMAIL"
-        # Fallback: try without VARIABLE_ prefix (Woodpecker 3.x may use different format)
-        [ -z "$USERNAME" ] && USERNAME="$CI_PIPELINE_DEPLOY_TASK"
-        echo "DEBUG: USERNAME=$USERNAME EMAIL=$EMAIL"
-        echo "DEBUG: All CI vars:" && env | grep ^CI_ | sort
         if [ -z "$USERNAME" ] || [ -z "$EMAIL" ]; then
           echo "ERROR: USERNAME and EMAIL variables are required"
+          echo "Trigger with: POST /api/repos/1/pipelines {branch:master, variables:{USERNAME:x, EMAIL:y}}"
           exit 1
         fi
         echo "Provisioning user: $USERNAME ($EMAIL)"