Cairn

Gateway config missing env var expansion in platforms

NousResearch/hermes-agent · cluster 119733

Data as of

Nothing open on GitHub. Fix merged in #120072. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #120072. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #120072. That is separate from the fix event.
Still open
Nothing open on GitHub.

A bug was identified where ${VAR} environment variable substitution was not being applied to gateway platform configuration fields (such as webhook secrets, API keys, and team credentials). Multiple fixes and follow-up patches address expanding env var references during gateway config loading.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #120072 gateway config: env refs expand for platforms.* and WEBHOOK_SECRET/PORT apply to a yaml-enabled webhook (#119733 #119763; salvage #119755/#119765, supersede #119737 #119750 #119770)

    merged to main

    files: gateway/config_env.py, gateway/config_loader.py, tests/gateway/test_config.py

3 PRs closed without merging

From the close comments: superseded by another PR 2 · merged via another change 1

  • #119737 fix(gateway): expand ${VAR} env substitutions in gateway config load · superseded by another PR → 004fa2e, #120072
  • #119750 fix(gateway): expand env-var refs in platform config loader · superseded by another PR → 004fa2e, #120072
  • #119755 fix(gateway): expand ${VAR} env refs in platform adapter config · merged via another change → 004fa2e, #120072
Closed issues · 1
  • Closed#119733[Bug]: ${VAR} env var substitution in config.yaml is not expanded for gateway platform config (platforms.*.extra — webhook secret, api_server key, teams credentials)
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.40: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Merged PRs
#120072
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
23 Sep 2026

For your agent

The same facts, typed.

cluster/119733.json
cluster/119733.md