Skip to content

feat(flash): fygaro-webhook workload — deployment, service, ingress (chart 3.2.54) - #253

Merged
islandbitcoin merged 2 commits into
mainfrom
feat/fygaro-webhook-workload
Aug 8, 2026
Merged

feat(flash): fygaro-webhook workload — deployment, service, ingress (chart 3.2.54)#253
islandbitcoin merged 2 commits into
mainfrom
feat/fygaro-webhook-workload

Conversation

@islandbitcoin

@islandbitcoin islandbitcoin commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

Companion to lnflash/flash#472 (Fygaro card top-up payment webhook) and lnflash/flash-mobile#685.

Mirrors the bridge-webhook workload 1:1 — same env surface, config-secret mount, probes, and enabled-gating:

  • Templates: fygaro-webhook-deployment.yaml, fygaro-webhook-service.yaml, fygaro-ingress.yaml — all gated on galoy.fygaro.webhook.enabled (default off)
  • Values: galoy.fygaro.webhook workload block (port 4010, replicas/probes/ingress mirroring bridge). The fygaro app-config block deliberately does NOT ship in default galoy.config: the app schema is additionalProperties: false at the root, so images predating flash#472 crash-loop on the unknown key (the dev-setup smoketest caught exactly this). Add galoy.config.fygaro + HMAC secrets via deployments overlays only after the flash image includes the fygaro schema; newer images default the feature off when the key is absent.
  • Helper: galoy.fygaro.webhook.fullname
  • Chart version 3.2.52 → 3.2.53

Render-verified (deps stripped locally): enabled=true produces the Deployment (entrypoint lib/servers/fygaro-webhook-server.js), Service, and Ingress; the default render produces no fygaro workload while the fygaro config block still reaches custom.yaml for the app schema. helm lint clean (pre-existing unvendored-dependency warning only).

Rollout note: merge order is flash#472 (image) → this chart → deployments overlay adding the hook host + secrets → configure the Hook URL in Fygaro's dashboard.

🤖 Generated with Claude Code

https://claude.ai/code/session_01NcEjF6SS3Ci5D4CzZqdPjb

Dread and others added 2 commits August 8, 2026 10:06
…chart 3.2.53)

Companion to lnflash/flash#472 (Fygaro card top-up payment webhook).
Mirrors the bridge-webhook workload 1:1: same env surface, config secret
mount, probes, and enabled-gating.

- templates: fygaro-webhook-deployment/-service/fygaro-ingress, rendered
  only when galoy.fygaro.webhook.enabled (default off)
- values: galoy.fygaro.webhook workload block (port 4010) and the
  `fygaro` app-config block under galoy.config (default-off; HMAC
  secrets injected per environment via deployments overlays)
- helper: galoy.fygaro.webhook.fullname

Render-verified: enabled=true produces all three objects with the
fygaro-webhook-server entrypoint; default renders no workload while the
fygaro config still reaches custom.yaml.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NcEjF6SS3Ci5D4CzZqdPjb
…h on unknown keys

The app config schema is additionalProperties:false at the root, so the
currently-pinned image rejects the fygaro key in custom.yaml and every
config-loading pod crash-loops (api/trigger/websocket/exporter/
ibex-webhook) — which is exactly what the dev-setup smoketest caught.

The fygaro config block moves to deployments overlays, added only after
the flash image includes the fygaro schema (which defaults the feature
off when the key is absent). The chart keeps only the workload block,
which renders nothing while disabled.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NcEjF6SS3Ci5D4CzZqdPjb
@islandbitcoin islandbitcoin changed the title feat(flash): fygaro-webhook workload — deployment, service, ingress (chart 3.2.53) feat(flash): fygaro-webhook workload — deployment, service, ingress (chart 3.2.54) Aug 8, 2026
@islandbitcoin
islandbitcoin force-pushed the feat/fygaro-webhook-workload branch from f281513 to 87aaf52 Compare August 8, 2026 17:07
@islandbitcoin
islandbitcoin merged commit d4d99d6 into main Aug 8, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant