lemmego / cli / 39464760780

61%

push

github

Expose health endpoints, and offer the database session driver

Three gaps found by scaffolding a project and taking it all the way up,
which is the only check that finds this class of thing.

**Health endpoints 404'd.** api ships HealthChecker plus the three
handlers and registers no routes, so a generated project had nowhere to
point a container platform's health check — and every platform wants
one. internal/routes/health.go now mounts /health, /livez and /readyz,
and registers the checks, because endpoints with no checks answer
"healthy" having verified nothing, which is a green light wired to no
sensor. The database check uses db.Resolve rather than an ORM handle, so
it is identical whichever connector the project was generated with, and
it does a real Ping: a pool holding a connection object and a server
that has gone away look the same until something asks.

**The database session driver was unreachable.** api v0.6.5 added it and
the CLI offered only file, memory and redis. Three pieces were needed,
not one:

- The choice, the flag value, the prompt option, and a validate rule —
  it needs a database, so selecting it without one is refused up front
  rather than at boot.
- The sessions table, as a migration emitted only when the driver is
  selected. Its SQL branches on the dialect because scs ships a store
  per dialect and each reads `expiry` differently: BYTEA/TIMESTAMPTZ on
  Postgres, BLOB/TIMESTAMP(6) with a CHAR(43) key on MySQL, BLOB/REAL on
  SQLite. Raw SQL, since the schema belongs to the store rather than to
  this project.
- **&session.Provider{} moved after the connectors in providers.go.**
  The driver resolves the connection through db.Resolve, which finds
  nothing if the session provider runs first. Without this the option
  would scaffold cleanly and refuse to boot.

The gate grew three configurations, one per dialect, because the
migration is the only stub whose SQL branches on the database — so two
of the three branches wou... (continued)

8 of 10 new or added lines in 4 files covered. (80.0%)

1271 of 2128 relevant lines covered (59.73%)

48.49 hits per line