[wmadden-electric]

$ prisma deploy list --stage qa-99d5e9
Address                     Kind      Platform ID                    URL
a2-qa-99d5e9                project   proj_x46eyjv91k1femz0acf82vdt  —
a2-qa-99d5e9.auth           module    —                              —
a2-qa-99d5e9.auth.database  postgres  db_…                           —
a2-qa-99d5e9.auth.service   service   cps_…                          https://….ewr.prisma.build
a2-qa-99d5e9.storefront     service   cps_…                          https://….ewr.prisma.build

This adds prisma deploy list. It prints every node of a deployed app on one stage, with its address, kind, platform ID and URL. Without --stage it lists production. --json prints the same rows for scripts and agents.

Why

Since the address change in #384, every deployed node is named on the platform by its full address, such as shop.catalog.db. But nothing showed those addresses. Users and agents could only work them out by reading the code. This command shows them, and the platform ID next to each one. The planned platform commands that take an address (prisma service logs @pr-42:shop.api) need that.

How it works

A deploy already uploads the app's topology to the platform for each stage: one entry per node, keyed by the node's address. deploy list reads that topology. It then looks up each node's platform row (the Project, a service, a database or a bucket) by its logicalId on that stage's Branch.

• It finds the app and the stage the same way deploy does. The app name comes from the entry in prisma.config.ts, and --name and --entry work as on deploy. --stage is checked the same way too.
• It does not read the deploy state. Reading that requires the deploy lock, so it would clash with a deploy that is running.
• A node with no platform row, such as a module, lists with no ID. Only services have a URL, and it is the URL deploy prints.
• If no app, stage or topology is found, the command fails with DEPLOY.TARGET_NOT_FOUND.

The command lives in @prisma/composer-cli, next to emulator list, because it reads Prisma Cloud data. Two internal subpaths, @internal/lowering/deployed and @internal/cli/app-identity, give it the platform reads and the app-name lookup. They don't pull Alchemy into the CLI's startup. The table of which resource types get a database or bucket row is now one shared map, RESOURCE_ROW_KINDS, used by the command, the e2e scripts and the local emulators.

One step left: the prisma binary

The prisma binary from prisma/prisma-cli mounts each Composer command by name. prisma deploy list works only once prisma-cli adds "deploy list" next to "emulator list". That is a one-line follow-up PR, opened after a Composer release includes this command. Until then, the new CI check runs Composer's command code directly.

Testing

• Unit tests cover the join and the kind mapping, the command's three outputs, an invalid stage, a missing workspace, and every "nothing deployed" case.
• A new step in the e2e deploy action, "Verify deploy list", runs the command after every e2e deploy. It checks each node's kind, ID and URL against the platform.
• Manual QA on the real platform deployed storefront-auth to production and to a named stage, listed both, and checked a stage that doesn't exist. The named stage listed only its own rows. The test Project was deleted afterwards. The details are in .drive/projects/node-addressing/slices/a2-deploy-list/qa.md.

Alternatives considered

• Reading the deploy state instead of the topology. Rejected: it needs the deploy lock and would block or clash with a running deploy.
• A framework extension hook for "read what is deployed". Rejected for one command. emulator list set the pattern of putting Prisma Cloud commands in composer-cli.
• deploy show. Rejected: list is the verb for a collection.

Agent: victoria-52

🤖 Generated with Claude Code

[prisma-gizmo]

✅ Gizmo reviewed 844b31e — posted 0 inline comment(s) this pass.

Open findings: none

Change walkthrough

This incremental pass reviews the final polish on prisma deploy list: the review-record updates, release-wording corrections in the docs and skill, and a fix to the e2e verification script that makes it load configs containing an orm section.

Review record — .drive/.../reviews/code-review.md replaces the empty "Already addressed" section with per-finding fix commits (F01–F07). The cited commits exist on the branch with matching subjects, and the F03 claim checks out: RESOURCE_ROW_KINDS lives in lowering/src/resource-rows.ts and is consumed by the command, the emulators, and scripts/platform-identity.ts.

Docs and skill — deploying.md and SKILL.md reword the release claim from the speculative "first ships in the release after 8.0.0-rc.26" to the verifiable "needs a prisma CLI release that includes it; 8.0.0-rc.26 does not". Both files now say the same thing, which matches the workspace's prisma: 8.0.0-rc.26 catalog pin and the e2e script's own comment that the installed binary does not mount the command yet. This addresses review finding F07 without inventing a future version.

E2E script — scripts/e2e-verify-deploy-list.ts mounts a second, command-less family declaring ormConfigSection next to the Composer family, so the engine's config loader accepts example configs with an orm section. That is a real need, not defensive padding: the deploy-verify-destroy action runs the script with the example's working directory as cwd, and the e2e matrix includes examples/orm-demo, whose prisma.config.ts sets an orm: section. The new @prisma/orm-toolchain import resolves the same way the script's pre-existing undeclared @prisma/cli-engine import does (.npmrc sets node-linker=hoisted, giving a flat root node_modules), and the lockfile pins the package at 8.0.0-rc.20 in agreement with every other @prisma/orm-* pin, so the ORM-pin lint stays satisfied.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 4dc62e0e-6377-4720-9a9a-5bb735bcb5b3

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@prisma/composer@388

npm i https://pkg.pr.new/@prisma/composer-cli@388

npm i https://pkg.pr.new/@prisma/composer-prisma-cloud@388

commit: 844b31e

[prisma-gizmo]

New findings: 🟡 2 minor · trace

[prisma-gizmo]

New findings: none · trace

[prisma-gizmo]

No Gizmo finding is open and the head commit has been reviewed. Approving.