feat(prisma-cloud)!: prisma deploy stops copying secrets from your local environment to Prisma Cloud, and fails only when a service needs a missing one by wmadden-electric · Pull Request #426 · prisma/composer

docs(drive): platform-variables slice 2 spec and dispatch plan

wmadden-electric

and

claude

committed

08cc2f1

feat(prisma-cloud): the input document carries $platform markers, and boot leaves an unset variable out

wmadden-electric

and

claude

committed

b31a0b9

feat(prisma-cloud): one checker for platform variable names, and an extension graph check after Load

wmadden-electric

and

claude

committed

29006e9

feat(prisma-cloud): deploy preflight writes no variable, and fails only for one a service needs

wmadden-electric

and

claude

committed

cfdb120

feat(prisma-cloud): the deploy lists every platform variable with no value, and prisma dev needs only a required per-key param

wmadden-electric

and

claude

committed

43671a5

fix(prisma-cloud): no doc comment or message says the deploy fills a platform variable

wmadden-electric

and

claude

committed

2c519c0

docs(prisma-cloud): ADR-0064, and every record says the deploy fills no platform variable

wmadden-electric

and

claude

committed

b110774

docs(drive): slice 2 spec says what preflight runs after, and which rows Composer writes

wmadden-electric

and

claude

committed

0800bd6

ci(e2e): the storefront deploy job sets AUTH_SIGNING_SECRET on the platform after the first deploy stops

wmadden-electric

and

claude

committed

45706b5

fix(prisma-cloud): core carries the preflight findings to the deploy report, and both preflights name an unset array position

wmadden-electric

and

claude

committed

0ba55b1

docs(prisma-cloud): records say how the findings reach the deploy report, why a leading underscore is refused, and what a platform variable is

wmadden-electric

and

claude

committed

168f2fa

fix(cli): redaction keeps the <value> placeholder in a command that sets a secret-named variable

wmadden-electric

and

claude

committed

01cb893

style(cli): format the redaction test

wmadden-electric

and

claude

committed

c6d9b2d

fix(cli): redaction keeps only an exact <value> placeholder

wmadden-electric

and

claude

committed

8b553a8

Merge remote-tracking branch 'origin/main' into claude/platform-variables-s2

wmadden-electric

committed

48b5625

fix(prisma-cloud): round-2 review fixes for slice 2

wmadden-electric

and

claude

committed

f6f5df6

test(integration): an unset per-key param with a default no longer stops prisma dev

wmadden-electric

and

claude

committed

a000253

fix(prisma-cloud): round-3 review fixes for slice 2

wmadden-electric

and

claude

committed

3b45c3a

Navigation Menu

Repository navigation

feat(prisma-cloud)!: prisma deploy stops copying secrets from your local environment to Prisma Cloud, and fails only when a service needs a missing one - #426

feat(prisma-cloud)!: prisma deploy stops copying secrets from your local environment to Prisma Cloud, and fails only when a service needs a missing one#426
wmadden-electric merged 34 commits into
mainfrom
claude/platform-variables-s2

Commits on Nov 6, 2026

docs(drive): platform-variables slice 2 spec and dispatch plan

feat(prisma-cloud): the input document carries $platform markers, and boot leaves an unset variable out

feat(prisma-cloud): one checker for platform variable names, and an extension graph check after Load

feat(prisma-cloud): deploy preflight writes no variable, and fails only for one a service needs

feat(prisma-cloud): the deploy lists every platform variable with no value, and prisma dev needs only a required per-key param

fix(prisma-cloud): no doc comment or message says the deploy fills a platform variable

docs(prisma-cloud): ADR-0064, and every record says the deploy fills no platform variable

docs(drive): slice 2 spec says what preflight runs after, and which rows Composer writes

ci(e2e): the storefront deploy job sets AUTH_SIGNING_SECRET on the platform after the first deploy stops

fix(prisma-cloud): core carries the preflight findings to the deploy report, and both preflights name an unset array position

docs(prisma-cloud): records say how the findings reach the deploy report, why a leading underscore is refused, and what a platform variable is

fix(cli): redaction keeps the <value> placeholder in a command that sets a secret-named variable

style(cli): format the redaction test

fix(cli): redaction keeps only an exact <value> placeholder

Merge remote-tracking branch 'origin/main' into claude/platform-variables-s2

fix(prisma-cloud): round-2 review fixes for slice 2

test(integration): an unset per-key param with a default no longer stops prisma dev

fix(prisma-cloud): round-3 review fixes for slice 2

Commits on Nov 10, 2026

Merge remote-tracking branch 'origin/main' into claude/platform-variables-s2

docs(prisma-cloud): say the deploy does not copy local values to platform variables

ci(e2e): the first-deploy check is a script, not inline shell

docs(drive): review questions that catch shortcuts, comments, inline CI shell and absolute wording

ci(e2e): match variable names as words instead of building a regular expression from them

test(e2e): prove the signing secret reached auth with an HMAC of a random challenge

docs(platform-variables): state the deploy choice as current and in plain English

fix(input-document): plain boot errors, and $secret is no longer escaped

fix(core): plain wording in preflight errors and test names

fix(prisma-cloud): one formatter for missing variables, no re-exports, plain errors

fix(cli): set the findings variable through preflightFindingsEnv on every path

test(storefront-auth): prove the signing key with a key check value, not a signing endpoint

ci(e2e): one script runs the first deploy and sets the platform variables

docs(platform-variables): quote the rewritten param error and the at-least-one wording

test(integration): prisma dev names a missing variable with "read by service"

Merge remote-tracking branch 'origin/main' into claude/platform-variables-s2