Problem
deno deploy database list currently does not expose the Deno KV database UUID needed to connect to production/preview/local KV from local code:
await Deno.openKv("https://api.deno.com/v2/databases/${DB_ID}/connect");This means non-interactive tools/coding agents can authenticate with an organization deploy token (ddo_...) and list databases, but still need a human to open the Console UI and copy the database ID.
Current behavior
Example command:
deno deploy database list --org <org-slug> --token <ddo_...>
The command lists database instances and environment rows, but for Deno KV the connection details are empty and the per-environment connect UUID is not shown.
Desired behavior
Expose the Deno KV connect database ID in a supported CLI/API surface, ideally in a machine-readable form. For example:
deno deploy database list --org <org-slug> --token <ddo_...> --json
with each KV environment including something like:
{
"instance": "my-kv",
"environment": "production",
"databaseId": "...",
"connectUrl": "https://api.deno.com/v2/databases/.../connect"
}Plain table output could also include the ID, but the important part is that agents/scripts can discover it without Console UI interaction.
Notes
The Console-side data already has the connect UUID per KV database environment; the gap is that it is not exposed as a stable public CLI/API contract.
Problem
deno deploy database listcurrently does not expose the Deno KV database UUID needed to connect to production/preview/local KV from local code:This means non-interactive tools/coding agents can authenticate with an organization deploy token (
ddo_...) and list databases, but still need a human to open the Console UI and copy the database ID.Current behavior
Example command:
The command lists database instances and environment rows, but for Deno KV the connection details are empty and the per-environment connect UUID is not shown.
Desired behavior
Expose the Deno KV connect database ID in a supported CLI/API surface, ideally in a machine-readable form. For example:
with each KV environment including something like:
{ "instance": "my-kv", "environment": "production", "databaseId": "...", "connectUrl": "https://api.deno.com/v2/databases/.../connect" }Plain table output could also include the ID, but the important part is that agents/scripts can discover it without Console UI interaction.
Notes
The Console-side data already has the connect UUID per KV database environment; the gap is that it is not exposed as a stable public CLI/API contract.