Skip to content

refactor: remove AGENT_TOKEN, use HUB_INTERNAL_VALIDATE_SECRET everywhere - #44

Merged
DominikPinsel merged 1 commit into
mainfrom
fix/remove-agent-token
Aug 8, 2026
Merged

refactor: remove AGENT_TOKEN, use HUB_INTERNAL_VALIDATE_SECRET everywhere#44
DominikPinsel merged 1 commit into
mainfrom
fix/remove-agent-token

Conversation

@DominikPinsel

Copy link
Copy Markdown
Owner

Follow-up to #42. AGENT_TOKEN always carried the same shared hub-internal secret under a misleading per-agent-sounding name — a mis-set value broke the claim path (incident 2026-08-07). Now that the platform injects HUB_INTERNAL_VALIDATE_SECRET into every agent container, the legacy name has no purpose:

  • operator: stop injecting/reserving AGENT_TOKEN; only HUB_INTERNAL_VALIDATE_SECRET remains platform-managed
  • runner: resolveInternalToken requires HUB_INTERNAL_VALIDATE_SECRET, fallback removed
  • docs/READMEs updated

Tests: operator envtest 38/38, runner 75/75.

…here

AGENT_TOKEN always carried the same shared hub-internal secret under a
misleading per-agent-sounding name; a mis-set value broke the claim
path (incident 2026-08-07). With the platform now injecting
HUB_INTERNAL_VALIDATE_SECRET into every agent container, the legacy
name has no purpose left:

- operator: stop injecting and reserving AGENT_TOKEN; only
  HUB_INTERNAL_VALIDATE_SECRET remains platform-managed
- runner: resolveInternalToken requires HUB_INTERNAL_VALIDATE_SECRET,
  no AGENT_TOKEN fallback
- docs/READMEs updated
@DominikPinsel
DominikPinsel merged commit b4ebe25 into main Aug 8, 2026
5 checks passed
@DominikPinsel
DominikPinsel deleted the fix/remove-agent-token branch August 8, 2026 10:20
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