Skip to content

Use GCS-backed IO manager for durable asset I/O #76

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
Jun 25, 2026
Merged

Use GCS-backed IO manager for durable asset I/O #76

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
10 changes: 10 additions & 0 deletions orchestration/definitions.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@

import dagster as dg
import yaml
from dagster_gcp.gcs import GCSPickleIOManager, GCSResource as DagsterGCSResource

from orchestration.resources.die_config import DIEConfigResource
from orchestration.resources.gcs import GCSResource
Expand Down Expand Up @@ -59,5 +60,14 @@ def _build_schedules(products_config: dict) -> list:
bucket_name=_products_config.get("gcs_bucket", "dataservices-die-products"),
),
"geoserver": GeoServerResource(),
# Persist asset I/O to GCS instead of the serverless run's ephemeral
# /tmp. Without this, materializing a downstream asset (combine /
# geoserver) on its own can't load its source inputs from a prior run
# and fails with FileNotFoundError.
"io_manager": GCSPickleIOManager(
gcs=DagsterGCSResource(),
gcs_bucket=_products_config.get("gcs_bucket", "dataservices-die-products"),
gcs_prefix="dagster-io",
),
},
)
Loading