Skip to content

Commit f5ae7f9

Browse files
authored
Merge pull request #76 from DataIntegrationGroup/feature/gcs-io-manager
Use GCS-backed IO manager for durable asset I/O
2 parents 1130565 + a5a8500 commit f5ae7f9

1 file changed

Lines changed: 10 additions & 0 deletions

File tree

orchestration/definitions.py

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22

33
import dagster as dg
44
import yaml
5+
from dagster_gcp.gcs import GCSPickleIOManager, GCSResource as DagsterGCSResource
56

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

0 commit comments

Comments
 (0)