Repository navigation
feat(lab): garuda's ingest token, and its own age key (#921) - #1144
Merged
Merged
Conversation
Runbook §6 for garuda, as run on 2026-10-10: - .sops.yaml: garuda's key (from `make secrets-init STACK=analyst` on garuda) in place of the analyst placeholder. - secrets/analyst.sops.yaml: INGEST_TOKEN, encrypted to garuda alone. - secrets/lab.sops.yaml: INGEST_TOKEN_GARUDA, set on alexander. The same value as garuda's; set on both from stdin, never an argument, and the hashes compared. - The lab side, in the five places eden's went: the Caddyfile map and header, the caddy environment, render-config.sh's COMPOSE_VARS, seed-validation-env.sh and lab.example.yaml; plus the README's clients. - Runbook §6: age and sops on Kali, and the checkout at ~/code/Gerrrt. alexander's `make up STACK=lab` and garuda's `make up STACK=analyst` follow the merge. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
🟢 Approval recommended
The token, recipient, proxy, rendering, validation, and documentation changes are complete and internally consistent.
0 open findings
What changed in this PR
Adds authenticated telemetry ingestion for garuda, completing runbook §6 of issue #921.
Changes:
- Adds matching encrypted ingest tokens for
garudaandalexander. - Registers
garudawith the lab Caddy proxy and rendering workflow. - Documents SOPS installation, key initialization, and deployment.
| File | Description |
|---|---|
.sops.yaml |
Registers garuda’s age recipient. |
docs/runbooks/build-the-analyst-workstation.md |
Documents setup and deployment. |
scripts/render-config.sh |
Renders the new token. |
scripts/seed-validation-env.sh |
Seeds validation credentials. |
secrets/analyst.sops.yaml |
Adds garuda’s encrypted token. |
secrets/lab.example.yaml |
Documents the lab-side token. |
secrets/lab.sops.yaml |
Adds the encrypted proxy token. |
stacks/lab/Caddyfile |
Authorizes garuda ingestion. |
stacks/lab/compose.yaml |
Supplies the token to Caddy. |
stacks/lab/README.md |
Updates the documented client list. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
This was referenced Oct 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is runbook §6 for
garuda, the analyst workstation. It is the PR that letsgaruda's Alloy push toalexander.Encrypted values, made on the hosts
.sops.yaml: garuda's own key replaces theanalystplaceholder. It was written bymake secrets-init STACK=analyston garuda.secrets/analyst.sops.yaml:INGEST_TOKEN, readable only by garuda.secrets/lab.sops.yaml:INGEST_TOKEN_GARUDA, set onalexander.make secrets-edit, with an editor that reads the value from the environment, so it was never an argument.alexander'slab.sops.yamlwas identical tomain's beforehand.The lab side, in the same places as eden's (#834's rule: the name and the value land together, or
alexander's next render fails):stacks/lab/Caddyfile: map entrygaruda agent, plus the client list.stacks/lab/compose.yaml: the caddy environment.scripts/render-config.sh:COMPOSE_VARS.scripts/seed-validation-env.sh.secrets/lab.example.yaml.stacks/lab/README.md: the client count.Runbook §6: Kali has
agebut notsops. It now installs the checksummedsops3.9.4 release binary, matchingalexander, and clones to~/code/Gerrrt/HomeLab.After merge:
make up STACK=labonalexander, thenmake up STACK=analyston garuda.validate.shpasses locally; checks that need Docker are left to CI.🤖 Generated with Claude Code