The YAML file for our DAG lays out how the DAG should be setup. Let’s break it down below:
This section provides a set of default_args that we can re-use. This provides access to the same default interface that is used in a normal python-DAG definition:
In these next few lines, we see a DAG definition. A few things to note:
The example DAG above overrides the owner from our default args. In addition it runs a custom Python function from our print_hello.py file. This demonstrates how executable python code (written by engineering team members) can be included with the no-code template.
The remaining DAGs just spawn simple bash operators with commands. Note however that multiple DAGs can be templated in one file. This can enable teams to submit DAG definitions or to otherwise group DAGs relating to a particular use case.
Let’s go over to the Admin UI to see these DAGs in action.