Ingredients¶
In addition to doing data work for data pipelines, Automation recipe variations can also be built to automate the provisioning and configuration of infrastructure to run data pipelines; to store common processes for reuse by multiple recipes; and to nest variations for a processing hierarchy.
These recipe variations can be declared as ingredients. Ingredients can be:
- Incorporated into, and reused by, other recipes.
- Called during the create and delete kitchen processes.
A recipe with ingredient variations is known as an ingredient provider.
Sub-process¶
When another process calls ingredients, the ingredients execute their functions as sub-processes.
Note
Ingredient nodes generate separate order runs. When a recipe variation containing an ingredient node calls the underlying ingredient, that ingredient runs in a different, temporary child kitchen and executes through a new order run of a separate order.
For example, a kitchen wizard can use ingredients to spin up and tear down infrastructure instances, and provision and delete data assets to support distinct development environments.
Related topics¶
Call Ingredients from Kitchen Wizard