Add on demand checks for Codra dependencies

Abierto
#157 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
38/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
docker, node.js, postgresql, typescript

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
TypeScript
Estrellas
125
Forks
23
Merge medio
2 d 13 h
PR fusionados (30 d)
12

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de devarshishimpi/codra

Todos los issues de devarshishimpi/codra

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.