Adds a second named wiki API key. The value is already in OpenBao (homelab/apps/ai/wiki-api-keys, property paperclip, version 4, minted with openssl rand -hex 32, no trailing newline this time). This PR maps it to Auth__ApiKeys__paperclip; facts and answers written with it are attributed as captured_by: paperclip. Reloader restarts the pod once the Secret changes.
Adds a second named wiki API key. The value is already in OpenBao (`homelab/apps/ai/wiki-api-keys`, property `paperclip`, version 4, minted with `openssl rand -hex 32`, no trailing newline this time). This PR maps it to `Auth__ApiKeys__paperclip`; facts and answers written with it are attributed as `captured_by: paperclip`. Reloader restarts the pod once the Secret changes.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Second named key in apps/ai/wiki-api-keys (OpenBao version 4), mapped to
Auth__ApiKeys__paperclip; writes through the API are attributed to it.
Reloader rolls the pod when the Secret changes.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
🤖Automated review — model CLI default (complexity: unknown), commit f732528551c55ea986fd51787ab84c906567cc33.
Advisory review by the review-bot pipeline. It never approves; a human merges. Push new commits to get a fresh review.
Summary
Adds a second named API-key entry (paperclip) to the existing wiki-api-keysExternalSecret in kubernetes/apps/wiki/externalsecrets.yaml, mirroring the pre-existing workstation entry exactly. No blocking issues found.
Tests
This is a GitOps manifest change, not application code — no unit tests apply. The change carries its own "test": ESO must be able to resolve apps/ai/wiki-api-keys / paperclip from OpenBao, and wiki-deployment.yaml's envFrom: secretRef: wiki-api-keys plus the existing secret.reloader.stakater.com/reload: ...,wiki-api-keys,... annotation (kubernetes/apps/wiki/deployment.yaml:27,79-80) will pick up the new env var and roll the pod automatically — no deployment changes were needed or made, which is correct.
Verification notes
The new block (kubernetes/apps/wiki/externalsecrets.yaml:45-48) matches the structure, indentation, and naming convention (Auth__ApiKeys__<name> / remoteRef.property: <name>) of the existing workstation entry (lines 41-44) exactly.
No secret values are committed — only a reference to an OpenBao path/property, consistent with the rest of the file.
Confirmed via kubernetes/apps/wiki/deployment.yaml that wiki-api-keys is consumed wholesale via envFrom.secretRef (not individual key references), so no other file needs updating for the new key to reach the pod.
The block comment at externalsecrets.yaml:27 ("One API key per machine identity... field = name") already documents this pattern, so no new comment was needed.
Could not verify from this repo that the Wiki application (external konairius/wiki image) actually maps the paperclip identity to captured_by: paperclip as claimed in the PR body — that logic lives outside this repository and isn't checkable here. This is consistent with how workstation was added previously, so it's a reasonable, low-risk assumption rather than a defect.
Recommendation
Looks reasonable — no blocking issues; comments above are informational only.
🤖 **Automated review** — model `CLI default` (complexity: unknown), commit `f732528551c55ea986fd51787ab84c906567cc33`.
> Advisory review by the `review-bot` pipeline. It never approves; a human merges. Push new commits to get a fresh review.
---
## Summary
Adds a second named API-key entry (`paperclip`) to the existing `wiki-api-keys` `ExternalSecret` in `kubernetes/apps/wiki/externalsecrets.yaml`, mirroring the pre-existing `workstation` entry exactly. No blocking issues found.
## Tests
This is a GitOps manifest change, not application code — no unit tests apply. The change carries its own "test": ESO must be able to resolve `apps/ai/wiki-api-keys` / `paperclip` from OpenBao, and `wiki-deployment.yaml`'s `envFrom: secretRef: wiki-api-keys` plus the existing `secret.reloader.stakater.com/reload: ...,wiki-api-keys,...` annotation (`kubernetes/apps/wiki/deployment.yaml:27,79-80`) will pick up the new env var and roll the pod automatically — no deployment changes were needed or made, which is correct.
## Verification notes
- The new block (`kubernetes/apps/wiki/externalsecrets.yaml:45-48`) matches the structure, indentation, and naming convention (`Auth__ApiKeys__<name>` / `remoteRef.property: <name>`) of the existing `workstation` entry (lines 41-44) exactly.
- No secret values are committed — only a reference to an OpenBao path/property, consistent with the rest of the file.
- Confirmed via `kubernetes/apps/wiki/deployment.yaml` that `wiki-api-keys` is consumed wholesale via `envFrom.secretRef` (not individual key references), so no other file needs updating for the new key to reach the pod.
- The block comment at `externalsecrets.yaml:27` ("One API key per machine identity... field = name") already documents this pattern, so no new comment was needed.
- Could not verify from this repo that the Wiki application (external `konairius/wiki` image) actually maps the `paperclip` identity to `captured_by: paperclip` as claimed in the PR body — that logic lives outside this repository and isn't checkable here. This is consistent with how `workstation` was added previously, so it's a reasonable, low-risk assumption rather than a defect.
## Recommendation
Looks reasonable — no blocking issues; comments above are informational only.
<!-- pr-review:sha=f732528551c55ea986fd51787ab84c906567cc33 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Adds a second named wiki API key. The value is already in OpenBao (
homelab/apps/ai/wiki-api-keys, propertypaperclip, version 4, minted withopenssl rand -hex 32, no trailing newline this time). This PR maps it toAuth__ApiKeys__paperclip; facts and answers written with it are attributed ascaptured_by: paperclip. Reloader restarts the pod once the Secret changes.🤖 Generated with Claude Code
🤖 Automated review — model
CLI default(complexity: unknown), commitf732528551c55ea986fd51787ab84c906567cc33.Summary
Adds a second named API-key entry (
paperclip) to the existingwiki-api-keysExternalSecretinkubernetes/apps/wiki/externalsecrets.yaml, mirroring the pre-existingworkstationentry exactly. No blocking issues found.Tests
This is a GitOps manifest change, not application code — no unit tests apply. The change carries its own "test": ESO must be able to resolve
apps/ai/wiki-api-keys/paperclipfrom OpenBao, andwiki-deployment.yaml'senvFrom: secretRef: wiki-api-keysplus the existingsecret.reloader.stakater.com/reload: ...,wiki-api-keys,...annotation (kubernetes/apps/wiki/deployment.yaml:27,79-80) will pick up the new env var and roll the pod automatically — no deployment changes were needed or made, which is correct.Verification notes
kubernetes/apps/wiki/externalsecrets.yaml:45-48) matches the structure, indentation, and naming convention (Auth__ApiKeys__<name>/remoteRef.property: <name>) of the existingworkstationentry (lines 41-44) exactly.kubernetes/apps/wiki/deployment.yamlthatwiki-api-keysis consumed wholesale viaenvFrom.secretRef(not individual key references), so no other file needs updating for the new key to reach the pod.externalsecrets.yaml:27("One API key per machine identity... field = name") already documents this pattern, so no new comment was needed.konairius/wikiimage) actually maps thepaperclipidentity tocaptured_by: paperclipas claimed in the PR body — that logic lives outside this repository and isn't checkable here. This is consistent with howworkstationwas added previously, so it's a reasonable, low-risk assumption rather than a defect.Recommendation
Looks reasonable — no blocking issues; comments above are informational only.