Gusty

- **`task_group_defaults`** - pass a default task group configuration as a dictionary to the `create_dag` function, which will take any parameter from Airflow's TaskGroup Class

- **`METADATA.yml` support** - Task groups can also be configured with a `METADATA.yml` file in their folder, just like DAGs

- **prefix_group_id off by default** - Explicitly set when you want a task group's id prefixed to each task group's task.

- **suffix_group_id** - A gusty exclusive! Explicitly set when you want a task group's id suffixed to each task group's task.

- **smart dependencies** (dependency levels) - A task can depend on any other task, regardless of task group. Task groups can depend on only other tasks / task groups that are their siblings.

- **smart dependencies** (prefixes/suffixes) - If tasks depend on other tasks in their task group, where the task group specifies a prefix or a suffix, the prefixed/suffixed dependency id will be added to the list of task group dependencies automatically


The full gusty 0.3.0 release notes can be found [here](https://github.com/chriscardillo/gusty/releases/tag/v0.3.0).

Airflow 2.0 is here and operators can now come from many different places ("providers"). To account for this, gusty 0.2.0 requires a full module.operator string be passed to the operator parameter in a YAML spec. This demo release is the structurally same as the Airflow 1.x Demo, but accounts for the package/application updates of both Airflow 2.0 and gusty 0.2.0.

The older demo contains separate containers for Jupyter and Rmd jobs, which are triggered via gusty operators, which have since been deprecated in gusty 0.1.0 in favor of custom operators.