python-dagster-to-orchestra

Python: Dagster -> Orchestra Conversion

Overview

Dagster's @op and @asset run Python inline in the Dagster executor — the logic lives right there in the op/asset function, not in a separate repo checked out at runtime. Orchestra's Python integration (Execute Script) has two modes: source: INLINE runs code pasted directly into parameters.code, and source: GIT runs a file checked out from a Git repo via parameters.command. Default to INLINE — it matches what Dagster already does and skips the extra step of extracting the body to a file and wiring a Git connection. Only use GIT when the op/asset itself checks out and runs a script from an already-separate repo.

Parameter Mapping

Orchestra YAML Structure

version: v1
name: <pipeline-name>
pipeline:
  <stage-uuid>:
    tasks:
      <task-uuid>:
        integration: PYTHON
        integration_job: PYTHON_EXECUTE_SCRIPT
        name: <op/asset name>
        connection: null                          # usually null for INLINE — set only if the code needs a specific connection's secrets
        parameters:
          source: INLINE                           # default — code already lives in the op/asset, no Git repo involved
          code: |
            <op/asset body, copied verbatim>
          build_command: 'pip install pandas'      # optional — only for non-stdlib imports
          python_version: '3.12'
        depends_on: []
        condition: null
        tags: []