supabase / cli / 36889927344
67%
develop: 67%

LAST BUILD BRANCH: gh-readonly-queue/develop/pr-6992-e1bea577b3db93ab45b65ff900a2aa5551b3bebb
DEFAULT BRANCH: develop
Ran
Jobs 1
Files 79
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 66.737%. Remained the same
36889927344

push

github

web-flow 
feat(cli): tag command telemetry with stack backend and OrioleDB (#6940)

## Summary

**TL;DR:** `cli_command_executed` now records which local backend a
command ran on (`stack_backend`: `legacy` or `stack`), which runtime its
stack uses (`stack_runtime`: `docker`, `podman`, or `native`), and
whether the project selects an OrioleDB image (`orioledb`). With these,
error rates can be compared per command between the legacy and new stack
backends (and per container or native runtime), and between OrioleDB and
standard Postgres projects, before the new stack becomes the default.

### Before

```mermaid
flowchart LR
  A["supabase &lt;command&gt;"] --> B["resolve backend<br/>(legacy for unrouted)"]
  B --> C["handler runs"]
  C --> D["cli_command_executed<br/>no backend, no engine"]
```

### After

```mermaid
flowchart LR
  A["supabase &lt;command&gt;"] --> B{"routed by<br/>experimental.stack?"}
  B -->|yes| C["StackBackendContext<br/>legacy or stack"]
  B -->|no| D["no backend"]
  C --> E["handler runs"]
  D --> E
  E --> F["config read records<br/>orioledb true/false"]
  E --> R["stack lookup records<br/>stack_runtime"]
  F --> G["cli_command_executed<br/>+ stack_backend<br/>+ orioledb<br/>+ stack_runtime"]
  R --> G
```

## Why

Command telemetry had no way to tell whether a command ran on the new
stack runtime or the legacy one, so we couldn't measure the new
runtime's adoption or failure rate. It also couldn't separate OrioleDB
projects from standard Postgres ones.

## What changed

- `resolveStackBackend` returns no backend for commands that
`experimental.stack` does not route (and for `--version`). The root
command provides `StackBackendContext` only when a backend was selected.
Handlers still default to legacy, so routing behavior is unchanged.
- `withCommandTelemetry` adds `stack_backend` when a backend was
selected. It also provides a command-scoped attribute sink, so code
below the handler can add properties to the command event.
- `orioledb` is ... (continued)

4097 of 6139 relevant lines covered (66.74%)

7.37 hits per line

Jobs
ID Job ID Ran Files Coverage
1 36889927344.1 79
66.74
GitHub Action Run
Source Files on build 36889927344