Skip to content

fix(pipedream): shared pipeline-level env vars no longer overridable at trigger time - #103

Merged
mchen-sentry merged 2 commits into
mainfrom
mingchen/pipeline-level-env-vars
Sep 10, 2026
Merged

mchen-sentry merged 2 commits into
mainfrom
mingchen/pipeline-level-env-vars

Conversation

@mchen-sentry

@mchen-sentry mchen-sentry commented Sep 10, 2026

Copy link
Copy Markdown
Member

Since the grouped pipedream update, every env var a service sets gets pushed down to the stage or job level, so nothing is left at the pipeline level.

GoCD's "Trigger with options" dialog only shows pipeline-level vars, which is why things like SKIP_CANARY_CHECKS disappeared from it and can't be flipped per run anymore.

The grouping change only checked that the scripts still see the same values at runtime (they do, since GoCD resolves job > stage > pipeline), and missed that the dialog reads from a different place.

Let's keep vars that are the same across all regions at the pipeline level so they show up in the dialog again.

Grouped pipelines demoted every service env var to stage or job level, so
variables like SKIP_CANARY_CHECKS disappeared from GoCD's Trigger with
options dialog and could no longer be overridden per run. Pipeline-level
vars identical across all regions in a group now stay at pipeline level.
@mchen-sentry
mchen-sentry marked this pull request as ready for review September 10, 2026 22:48
Comment thread libs/pipedream.libsonnet
@mchen-sentry
mchen-sentry merged commit 9de1ad0 into main Sep 10, 2026
10 checks passed
@mchen-sentry
mchen-sentry deleted the mingchen/pipeline-level-env-vars branch September 10, 2026 22:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants