chemavx/k8s-manifests
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(n8n): inyectar TELEGRAM_BOT_TOKEN/CHAT_ID desde telegram-notify-infisical

Browse Source 
Para que el workflow 'Health Check General' lea el token del bot de notificaciones
via process.env en vez de hardcodearlo (rotación 2026-07-09).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
chemavx
2026-07-09 20:54:21 +00:00
co-authored by Claude Fable 5
parent 43c78246a8
commit cbfb1ba039
1 changed files with 13 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
n8n/deployment-n8n.yaml
+13
View File
@@ -45,6 +45,19 @@ spec:
secretKeyRef: secretKeyRef:
name: n8n-secret-infisical name: n8n-secret-infisical
key: GETXAPI_TOKEN key: GETXAPI_TOKEN
# Token del bot @chemavx_bot (notificaciones) — rotado 2026-07-09.
# Lo consume el workflow "Health Check General" vía process.env,
# ya no hardcodeado. Fuente: Infisical homelab/prod/telegram.
- name: TELEGRAM_BOT_TOKEN
valueFrom:
secretKeyRef:
name: telegram-notify-infisical
key: TELEGRAM_BOT_TOKEN
- name: TELEGRAM_CHAT_ID
valueFrom:
secretKeyRef:
name: telegram-notify-infisical
key: TELEGRAM_CHAT_ID
# n8n ≥1.x bloquea $env en expresiones por defecto; sin esto el nodo # n8n ≥1.x bloquea $env en expresiones por defecto; sin esto el nodo
# HTTP del autopost no puede leer GETXAPI_TOKEN. Instancia single-user. # HTTP del autopost no puede leer GETXAPI_TOKEN. Instancia single-user.
- name: N8N_BLOCK_ENV_ACCESS_IN_NODE - name: N8N_BLOCK_ENV_ACCESS_IN_NODE