sam/pi-config
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

project-ops: document transient Vikunja 401 (retry once) in secrets section

Browse Source
This commit is contained in:
Sam Rolfe
2026-09-05 18:39:27 +10:00
parent b0f3858946
commit 956db72719
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
skills/project-ops/SKILL.md
View File

@@ -22,7 +22,7 @@ VIKUNJA_TOKEN=$(grep "^VIKUNJA_TOKEN=" ~/.config/environment.d/10-secrets.conf |
OL_API_KEY=$(grep "^OL_API_KEY=" ~/.config/environment.d/10-secrets.conf | head -1 | cut -d= -f2- | tr -d '"' | tr -d ' ') OL_API_KEY=$(grep "^OL_API_KEY=" ~/.config/environment.d/10-secrets.conf | head -1 | cut -d= -f2- | tr -d '"' | tr -d ' ')
``` ```
If token 401s: re-source or confirm the machine's secrets were pulled (`git -C ~/.agents pull`). If token 401s: **Vikunja sometimes intermittently rejects a valid token** (transient; observed on LAN). First **retry once** — the same call returning 401 then 200 with an identical token is a known flake, not a wrong value. Only if a retry still 401s: re-source the secrets (new shell/login) so the fresh value is read; if still failing, ask the user to confirm the token was regenerated in Vikunja and re-placed. Outline keys are stable (401 there = genuinely wrong key).
Never commit or echo the token values. Never commit or echo the token values.
## 2. Vikunja API (tasks, stages, progress) ## 2. Vikunja API (tasks, stages, progress)