The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

Is running 2 pipeline containers with different versions of dagster (i.e. `0.12` and `0.13`) a supported use case on the same deployment (i.e `0.13`), or should we prefer having 2 completely different deployments with each dagster versions?

For context, we noticed breaking changes between `0.12` and `0.13` with some of our existing pipelines. We would like to migrate incrementally, therefore needing to run both versions in parallel during the migration.

it should be possible to have pipeline containers on different versions in the same deployment - do you recall what the breaking change you ran into was? The intention was for 0.13.0 not be a breaking change

Ok perfect — thank you!

As for the breaking changes we found so far;
• `DagsterLogManager()` changed its inputs to accepting a `DagsterLogHandler` instead of `run_id`, `loggers`, etc. We define `OutputContext` that required this class as fixtures in tests we wrote for custom IOManagers.
• Something seems to have changed with `dagster_aws.create_s3_fake_resource` as I’m suddenly getting a `AttributeError: 'S3FakeSession' object has no attribute 'exceptions'`.
I stopped digging after these two and figured we would migrate incrementally if possible, which sounds like it is! :smile: