Page MenuHomePhabricator

Use execute_step_with_structured_logs in DagsterDockerOperator
ClosedPublic

Authored by dgibson on Tue, Oct 13, 8:31 PM.

Details

Summary

Extremely similar to https://dagster.phacility.com/D4752, but with dagster_airflow instead of dagster_celery_docker.

Test Plan

BK

Diff Detail

Repository
R1 dagster
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

test fixes, move test fixtures to dagster_airflow_tests

Harbormaster returned this revision to the author for changes because remote builds failed.Tue, Oct 13, 9:12 PM
Harbormaster failed remote builds in B19463: Diff 23650!
Harbormaster failed remote builds in B19465: Diff 23652!
Harbormaster returned this revision to the author for changes because remote builds failed.Tue, Oct 13, 9:44 PM
Harbormaster failed remote builds in B19469: Diff 23656!
Harbormaster returned this revision to the author for changes because remote builds failed.Wed, Oct 14, 2:20 AM
Harbormaster failed remote builds in B19478: Diff 23666!

solved the mystery of why this was not running in BK but celery-docker was. hopefully fix both

Harbormaster returned this revision to the author for changes because remote builds failed.Thu, Oct 15, 9:48 PM
Harbormaster failed remote builds in B19605: Diff 23812!
This revision is now accepted and ready to land.Mon, Oct 19, 4:08 PM