d497a874d2
fix: routes Fabio KV avec printf pour eviter rupture indentation YAML
...
ci/woodpecker/push/woodpecker Pipeline was successful
La variable multiline cassait le parser YAML (ligne sans indentation).
Utilisation de printf avec \n pour construire la chaine sur une seule ligne.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com >
2026-03-17 21:22:23 +01:00
d97b522162
feat: cert TLS automatique via acme-companion + route HTTPS Fabio
...
- Ajout label LETSENCRYPT_HOST sur le container prestashop :
sonic-acme-1 (acme-companion) emet le cert et le copie dans /host/certs/
Fabio le detecte par SNI sans redemarrage
- Route Fabio KV mise a jour : HTTP et HTTPS (domain:443) en une seule cle
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com >
2026-03-17 21:21:30 +01:00
2a75a274f6
deploy: ecriture route Fabio via Consul KV apres enregistrement service
...
ci/woodpecker/push/woodpecker Pipeline was successful
Fabio ne detecte pas toujours les nouveaux services via le catalog Consul.
Ajout d'un consul kv put fabio/config avec la route urlprefix apres chaque
deploiement pour garantir le routage sans redemarrage de Fabio.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com >
2026-03-17 21:03:53 +01:00
2513d3534d
fix: registration Consul via docker exec sonic-consul (supprime register-consul step)
...
ci/woodpecker/push/woodpecker Pipeline failed
- write-env ecrit le token dans .consul_token (workspace partage)
- deploy lit .consul_token et utilise docker exec sonic-consul pour
enregistrer le service directement sur l'agent consul local
- network_mode host non supporte par ce Woodpecker, 172.17.0.1:8500
ne rejoignait pas le meme consul que Fabio
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com >
2026-03-17 20:07:10 +01:00
9d1406c79d
fix: register-consul utilise network_mode host (localhost:8500 = consul reel)
...
172.17.0.1:8500 passe par les regles iptables DOCKER et n'atteint pas
le meme consul que Fabio. Avec host network, localhost:8500 est direct.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com >
2026-03-17 20:03:25 +01:00
6dec47a3bd
fix: ecrire .container_ip dans CI_WORKSPACE (cd /opt/prestashop changeait le CWD)
...
ci/woodpecker/push/woodpecker Pipeline failed
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com >
2026-03-17 19:57:46 +01:00
4ccddc69e3
fix: enregistrement manuel dans Consul (ACL bloque Registrator sur prestashop)
...
ci/woodpecker/push/woodpecker Pipeline failed
Ajout etape register-consul : recupere l'IP du conteneur sur le reseau sonic
et enregistre le service dans Consul avec le token ACL via l'API HTTP.
Registrator loggue "added" mais son token n'a pas les droits service:write
sur "prestashop" -> le service disparaissait de Consul apres chaque deploy.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com >
2026-03-17 19:55:15 +01:00
80ebfb0c5a
chore: trigger pipeline (prestashop install complete)
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 19:39:44 +01:00
1040f7272f
fix: healthcheck evite substitution Woodpecker (SITE au lieu de PS_DOMAIN)
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 19:10:45 +01:00
380d0cf7d1
fix: write-env utilise env|grep (bug Woodpecker: dollar-brace dans commands droppe secrets)
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 19:06:46 +01:00
abcc517e3c
debug: write-env-1 avec commande identique regression test
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 19:05:01 +01:00
d34e9b4922
debug: seul write-env-1 avec from_secret, les autres placeholder
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 19:01:35 +01:00
64262d1b1f
fix: 3 steps write-env (2 secrets max par step, bug Woodpecker)
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 18:57:59 +01:00
05f5401def
debug: seuil - TEST_STATIC + 3 from_secret
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 18:57:12 +01:00
0a5c13a1b6
debug: TEST_STATIC hello-world + 6 from_secret
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 18:56:06 +01:00
9f7af2f3c6
fix: DEPLOY_ENV comme valeur statique (CI etait deduplique)
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 18:54:08 +01:00
3c5a683540
fix: workaround bug Woodpecker - valeur statique CI requise pour from_secret
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 18:52:12 +01:00
3adeebc4aa
debug: test 1 statique + 2 from_secret
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 18:51:17 +01:00
50a31ad9ff
debug: regression test identique pipeline 26
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 18:49:15 +01:00
0401c0b3d9
debug: test valeur statique dummy + 2 from_secret
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 18:47:49 +01:00
74e84ea617
debug: test 2 from_secret (ps_domain + ps_admin_folder)
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 18:46:18 +01:00
3f4ddcf914
fix: healthcheck utilise alpine:3.20 + curl (curlimages sans grep)
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 18:42:27 +01:00
b21cd3dafe
fix: contournement bug volumes+from_secret, healthcheck lit depuis workspace
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 18:40:46 +01:00
295e96367e
debug: test volumes + from_secret sur docker:27-cli
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 18:38:31 +01:00
e001cf7d00
deploy: secrets OK, suppression debug-secrets, lancement deploiement
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 18:32:22 +01:00
d90bc558a2
debug: test from_secret ps_domain dans environment
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 18:31:31 +01:00
dc48cee578
debug: env | sort pour lister toutes les vars du container
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 18:30:07 +01:00
03bee992be
chore: test03 woodpecker sleep30s
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 18:28:54 +01:00
2c5be85a01
debug: sleep 30s in debug-secrets pour inspecter le container
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 18:27:08 +01:00
c2cd131ca8
chore: test02 woodpecker
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 18:23:43 +01:00
f6cf648c4c
debug: test secret injection vs static env var
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 16:50:20 +01:00
b26bbd8911
chore: test après restart woodpecker
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 16:38:54 +01:00
80bf3b5104
chore: debug
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 16:18:12 +01:00
c4e1c8bc82
chore: debug secrets transmission
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 16:15:28 +01:00
ff13a4efa8
fix: remove agent label filter (agent deleted)
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 16:12:35 +01:00
8bcee6b02d
chore: retrigger pipeline after secrets org_id fix
ci/woodpecker/push/woodpecker Pipeline is pending
2026-03-17 16:10:37 +01:00
50dd40ea14
chore: test secrets lowercase
2026-03-17 16:04:21 +01:00
269d7a7426
chore: test secrets lowercase
2026-03-17 16:02:40 +01:00
2662625d43
fix: use lowercase secret names (Woodpecker normalizes to lowercase)
2026-03-17 15:59:50 +01:00
8acc2576d4
chore: test secrets injection
2026-03-17 15:58:11 +01:00
61672a0125
chore: test secrets with correct org_id
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 15:26:36 +01:00
121668a98b
chore: test secrets after woodpecker restart
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 14:05:00 +01:00
17c183e460
debug: add secret injection diagnostic step
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 13:42:33 +01:00
72c84806f7
fix: use secrets array instead of from_secret
2026-03-17 13:41:09 +01:00
aeb3f46e2c
fix: migrate to woodpecker v3 list syntax, fix env generation
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 13:39:27 +01:00
d51d96f04c
chore: retrigger pipeline
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 13:27:06 +01:00
b17062f9af
fix: healthcheck - detect empty PS_DOMAIN and extend timeout to 10min
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 13:26:07 +01:00
f39c57bd5a
chore: retrigger pipeline after admin trust
ci/woodpecker/push/woodpecker Pipeline failed
2026-03-17 13:16:12 +01:00
5800638cc2
fix: quote all shell commands containing colons in YAML
2026-03-17 13:08:35 +01:00
2a2fa4d6f4
fix: quote shell command with colon to avoid YAML parse error
2026-03-17 13:07:31 +01:00
syoul