First deploy of a fresh stage fails in the ADR-0057 env-key check: "the address <service> is not inside the app <app>" (0.35.0; works on 0.34.0)

Aperta
#394 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
1-2 giorni
Idoneità per principianti
53/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
bun, next.js, node.js, typescript
Ambito
backend, devops

Direzione di ricerca

Start with packages/1-prisma-cloud/1-extensions/target/src/legacy-resource-ids.ts and env-key-clash.ts, tracing how a root-provisioned service's graph node id reaches addressBelowApp. Compare the 0.35.0 behavior with 0.34.0, then run the fresh-stage deploy reproduction described in the issue. Done means the 0.35.0 check accepts the root service address and the first deploy proceeds.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug
Package and version

@prisma/[email protected] (with @prisma/[email protected]), run by prisma CLI 8.0.0-rc.27 through prisma/cloud-deploy-action@v1 (bun run --bun prisma deploy module.ts --stage <branch>)

What happened?

Deploying a stage that has never been deployed before (no prior deploy state, no existing resources) fails at the environment variable check:

✔ connect to project and branch (2.4s)
✘ check environment variables (1ms)
✘ [DEPLOY.PREFLIGHT_FAILED] prisma-cloud: the address "web" is not inside the app "myapp".

The app is one Next.js compute service named web, provisioned directly in the root module, plus an ORM-typed postgres resource and two envSecret inputs. I retried with and without the bound platform variables present in the deploying shell and got the same error both times, so it doesn't seem to be about missing variables.

Side note: the docs URL printed under the error leads to the CLI error reference, which currently has no DEPLOY section. I'll raise that separately against prisma-cli.

What did you expect to happen?

The first deploy of a fresh stage provisions the declared resources and goes through. With both Composer packages pinned to 0.34.0, the exact same app and stage deploy fine.

Minimal reproduction
// module.ts
import { fileURLToPath } from 'node:url'
import { module } from '@prisma/composer'
import { envSecret } from '@prisma/composer-prisma-cloud'
import { postgres } from '@prisma/composer-prisma-cloud/orm'
import { appData } from './src/prisma/data'
import webService from './src/service'

const config = fileURLToPath(new URL('./prisma.config.ts', import.meta.url))

export default module('myapp', ({ provision }) => {
  const db = provision(postgres({ name: 'database', contract: appData, config }))
  provision(webService, {
    deps: { db },
    input: {
      authSecret: envSecret('AUTH_SECRET'),
      blobToken: envSecret('BLOB_TOKEN'),
    },
  })
})

// src/service.ts
export default compute({
  name: 'web',
  deps: { db: postgres(appData) },
  input: type({ authSecret: secretString(), blobToken: secretString() }),
  build: nextjs({ module: import.meta.url, appDir: '..' }),
})
  1. npm install @prisma/[email protected] @prisma/[email protected] (today's latest)
  2. npm run build (Next.js with output: 'standalone')
  3. prisma deploy module.ts --stage some-fresh-branch, against a stage that has never been deployed
  4. Fails as above. Pin both packages to 0.34.0 and the identical deploy succeeds.

I can share a reproduction repo if that helps.

From reading the published source (might be off, but in case it saves triage time): the message is thrown by addressBelowApp in packages/1-prisma-cloud/1-extensions/target/src/legacy-resource-ids.ts, which expects every address to start with ".". findEnvKeyClashes in env-key-clash.ts (new in 0.35.0) passes each service's graph node id into it, and for a service provisioned directly in the root module that id seems to be the bare service name ("web") rather than "myapp.web". 0.34.0 has neither file, which would explain why the pin works. The symptom timing looks similar to #103 but this seems like a different defect.

Environment
  • GitHub Actions ubuntu-latest, Node 24 (actions/setup-node), Bun via oven-sh/setup-bun@v2, npm
  • Prisma Cloud, OIDC through a Console-connected repository, region ap-northeast-1
  • Workaround: pin @prisma/composer and @prisma/composer-prisma-cloud to 0.34.0
Additional context

No response

Lingua principale
TypeScript
Stelle
6
Fork
2
Merge medio
1g 9h
PR unite (30g)
42

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di prisma/composer

Tutte le issue di prisma/composer

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.