Skip to content

ci: unbind the Dagster deploy from the production environment #859

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jirhiker merged 1 commit into from
Aug 19, 2026
Merged

ci: unbind the Dagster deploy from the production environment #859

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion .github/workflows/CD_dagster_prod.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,13 @@ concurrency:
jobs:
dagster-prod-deploy:
runs-on: ubuntu-latest
environment: production
# Deliberately not bound to the `production` GitHub environment. This job
# reads only repository-level DAGSTER_CLOUD_API_TOKEN and
# DAGSTER_CLOUD_ORGANIZATION_ID -- none of that environment's secrets -- and
# it runs on every push to `staging` that touches the code location. Binding
# it would put an approval gate on routine merges once `production` requires
# reviewers, which is a gate on the wrong thing: this publishes code, not
# data.

steps:
- name: Check out source repository
Expand Down
Loading