Simplify a Variation Graph

• Use Case: A variation running one phase of an Azure Data Factory (ADF) pipeline becomes complex with the addition of a reconciliation subroutine. The subroutine is configured as an ingredient instead, and an ingredient node in the variation calls that ingredient to run at the appropriate stage.
• Example Ingredient: In this example, the reconciliation subroutine is extracted from the pipeline graph, placed in a separate variation, and declared as an ingredient in order to simplify the pipeline and, perhaps, test and measure the performance of the subroutine separately.

An ingredient node calls an ingredient that is pre-configured to run a subroutine.

Ingredient Configuration

Before a user can configure an ingredient node to call this subroutine, the subroutine variation, itself, must be declared as an ingredient. See Declare Ingredients for more information.

This variation is declared as an ingredient and requires no input/output variables to configure.

Ingredient Node Configuration

With the subroutine ingredient pre-configured, the example variation can call it using an ingredient node.

This ingredient node calls the subroutine ingredient.

Ingredient node configuration starts with a "mapping" to the ingredient.