Add on demand checks for Codra dependencies

Offen
#157 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
38/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
docker, node.js, postgresql, typescript

Rechercherichtung

Start by reading the existing setup and runtime adapter code, then find where dependency checks can be started and how shared results are represented. Implement checks for the listed dependencies while preserving the stated on-demand PostgreSQL behavior and secret handling; verify success, failure, unavailable, and database cold start or timeout cases in both runtimes. Done means the requested checks and tests work and typecheck, test, and lint pass.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

enhancement good first issue help wanted

Goal

Build the backend checks used by Codra's manual setup and dependency check. The dashboard will start these checks and display their results in a separate subissue, #158.

Checks to support

Check the dependencies Codra can verify: GitHub App configuration and access, available webhook delivery information, model provider credentials, the configured queue or worker, and PostgreSQL. If the current runtime cannot verify a dependency, return an unavailable result instead of reporting a failure.

Important database behavior

PostgreSQL checks must happen only after an operator asks for them or when a normal Codra operation needs the database. A connection attempt may wake a suspended serverless database. Do not add scheduled probes, keep alive connections, or other behavior that prevents it from suspending. If a cold start or timeout occurs, report it clearly where possible.

Implementation guidance

Keep the check result format in shared code, and use the existing runtime adapters to perform checks that depend on Cloudflare or Node/Docker services. Do not expose API keys, private keys, or other secrets in results or logs. Check the current setup and permission state without changing it.

Done when

  • Each supported dependency returns passed, failed, or unavailable with a short explanation and next step.
  • PostgreSQL is checked on demand and is not kept awake.
  • The behavior works in both Cloudflare Workers and Node/Docker. Runtime specific checks may be unavailable when a runtime lacks the needed access.
  • Tests cover success, failure, unavailable results, and database cold start or timeout behavior.
  • npm run typecheck, npm test, and npm run lint all pass.
Vorherrschende Sprache
TypeScript
Sterne
125
Forks
23
Ø Merge
2 T. 13 Std.
Gemergte PRs (30 T.)
12

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus devarshishimpi/codra

Alle Issues in devarshishimpi/codra

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.