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)
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
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
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: '..' }),
})
- npm install @prisma/[email protected] @prisma/[email protected] (today's latest)
- npm run build (Next.js with output: 'standalone')
- prisma deploy module.ts --stage some-fresh-branch, against a stage that has never been deployed
- 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
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di prisma/composer
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 90/100
I maintainer di solito rispondono entro 1 giorno
-
@prisma/composer-prisma-cloud 0.36.0 peer-pins @prisma/orm-postgres 8.0.0-rc.20, so it cannot be installed next to the current ORM rc.22 without --legacy-peer-depsForse di nuovo libera Una pull request per questa issue è stata chiusa senza essere unita. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 45/100
I maintainer di solito rispondono entro 1 giorno
-
enhancement
Difficoltà 4/5 3-5 giorni Idoneità per principianti 42/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 52/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 35/100
prisma/composer#329 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di prisma/composer
Issue simili
-
dream report: normalizeMutation discards ok/status, consumers can only string-match the summaryAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
thecodacus/understory#61 ·
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
Termix-SSH/Plugin-Hosts-Config#14 · 1 commento ·
I maintainer di solito rispondono entro 4 giorni
-
ai-generated priority: p2 size: s type: bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
JonathanTSilva/jts-website#92 ·
I maintainer di solito rispondono entro 1 giorno
-
Toast announcer reads a doubled period when a toast's title ends in punctuationForse già presa Una pull request collegata a questa issue è aperta o già unita. Aperta
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
vercel-labs/ui#999 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
ehmpathy/rhachet-roles-ehmpathy#1443 ·
I maintainer di solito rispondono entro 1 giorno