Databricks Workflow¶
These real terminal captures use a historical development build. They are not current release certification; independent output review and current installed-wheel scenario checks remain pending.
Overview¶
This worked example compares workflow.yml. Advertised filename extensions: .yml, .yaml.
What changes¶
Add env parameter default prod and transform task pointing to /notebooks/transform with dependency on ingest; retain existing ingest task and job name.
Before¶
name: etl_job
tasks:
- task_key: ingest
notebook_task:
notebook_path: /notebooks/ingest
After¶
name: etl_job
parameters:
- name: env
default: prod
tasks:
- task_key: ingest
notebook_task:
notebook_path: /notebooks/ingest
- task_key: transform
depends_on:
- task_key: ingest
notebook_task:
notebook_path: /notebooks/transform
Things to know¶
-
env is not consumed by either shown notebook task.
-
Actual notebook existence and deployment validity are outside the source fixture.
Recorded output¶
Recorded from a real native CLI through rs-rich-record. A refactoring label does not prove equivalent behavior. Build identities.
Scenario coverage¶
| Scenario | Status |
|---|---|
| Meaningful edit | Source example reviewed; output captured; independent result certification pending |
| Unchanged content | Not yet certified for this candidate |
| Populate / clear a file | Not yet certified for this candidate |
| Add / delete an entity | Not yet certified for this candidate |
| Rename a symbol | Not yet certified for this candidate |
| Move / reorder code | Not yet certified for this candidate |
| Formatting only | Not yet certified for this candidate |
| Git file rename / move | Not yet certified for this candidate |
| Mixed move and edit | Not yet certified for this candidate |
| Invalid syntax / actionable error | Not yet certified for this candidate |
| Guardrail review | Not yet certified for this candidate |
Try it¶
Save the two source blocks as separate files with the shown extension, then compare them:
intentumdiff file before/workflow.yml after/workflow.yml
The installed Python wheel includes its parser components. The native CLI requires a component directory. Compare the result with the source change described above; agreement between APIs alone is not proof of correctness.