From ba2c53c15867a0b8f6caed03829d1fd0ea8eeb55 Mon Sep 17 00:00:00 2001
From: gitea_admin <gitea@local.domain>
Date: Wed, 1 Apr 2026 18:39:07 +0000
Subject: [PATCH] Actualiser .woodpecker/pipeline.yml

---
 .woodpecker/pipeline.yml | 30 ++++++++++++++----------------
 1 file changed, 14 insertions(+), 16 deletions(-)

diff --git a/.woodpecker/pipeline.yml b/.woodpecker/pipeline.yml
index eb82abb..a86d57e 100644
--- a/.woodpecker/pipeline.yml
+++ b/.woodpecker/pipeline.yml
@@ -4,25 +4,23 @@ name: full-devops-stack
 steps:
   # Étape 1 : Build & Push l'image vers le registre Gitea
   build-and-publish:
-    image: banzaicloud/kaniko-plugin
+    image: gcr.io/kaniko-project/executor:debug # Version debug pour avoir le shell
     environment:
-      KANIKO_FORCE: "true" 
-      # OU force le flag via une variable d'arguments
-      ARG_FORCE: "--force"
-      DOCKER_USERNAME:
+      REGISTRY_USER:
         from_secret: registry_user
-      DOCKER_PASSWORD:
+      REGISTRY_PASS:
         from_secret: registry_password
-    settings:
-      registry: gitea.213.165.95.242.sslip.io
-      repo: gitea_admin/hello-world
-      tags: latest,${CI_COMMIT_SHA:0:7}
-      username:
-        from_secret: docker_username
-      password:
-        from_secret: docker_password
-      # Pour autoriser le registre HTTP/auto-signé
-      extra_args: --force --insecure --skip-tls-verify
+    commands:
+      # 1. Créer le fichier d'auth Docker pour Gitea
+      - echo "{\"auths\":{\"gitea.213.165.95.242.sslip.io\":{\"username\":\"$REGISTRY_USER\",\"password\":\"$REGISTRY_PASS\"}}}" > /kaniko/.docker/config.json
+      # 2. Lancer Kaniko avec le flag --force explicitement
+      - /kaniko/executor 
+        --context $CI_WORKSPACE 
+        --dockerfile $CI_WORKSPACE/Dockerfile 
+        --destination gitea.213.165.95.242.sslip.io/gitea_admin/hello-world:${CI_COMMIT_SHA:0:7}
+        --insecure 
+        --skip-tls-verify 
+        --force
 
   # Étape 2 : Déploiement sur K3s
   deploy-to-k3s: