chrisfu dbe249ce9f fix(gitea): REST API bootstrap path bypasses broken admin CLI; fix DB namespace resolver ... deploy.sh: resolve_knoe_db_namespace() now checks DATABASE_NAMESPACE from config (k3s.cfg: knoe-db) before probing namespaces. Previously it fell back to 'default' because only 'knoe' was probed, baking a wrong DB hostname into app.ini. The running server was unaffected (uses GITEA__database__HOST env var) but the gitea admin CLI, which reads app.ini directly, could not connect. init_knoe_users.sh: add gitea_helm_admin_token() which reads the Helm bootstrap admin password from the gitea-gitea k8s secret and exchanges it for a REST API token — entirely avoiding the broken CLI. Add gitea_api_set_password() which uses PATCH /api/v1/admin/users/{user} to set the password via the running web server (which has the correct DB connection) instead of kubectl exec. promote_gitea_admin() now prefers the REST-API-only path: 1. existing token (env / k8s secret) 2. Helm admin k8s secret → REST token; set KNOE_ADMIN_PRINCIPAL password via API 3. 1Password → CLI set-password → basic-auth token (fallback) 4. kubectl exec generate-access-token (last resort) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>		2026-05-09 18:53:55 -07:00
..
spnego-proxy	fix(spnego-proxy): add statusCapture to log SPNEGO auth failures	2026-05-08 21:43:20 -07:00
deploy.sh	fix(gitea): REST API bootstrap path bypasses broken admin CLI; fix DB namespace resolver	2026-05-09 18:53:55 -07:00