Summary
With the completion of this chapter, you’ve got a system that can be used to allow “non-technical” users to author and execute workflows without having any understanding of Airflow (or even Python). This is a powerful pattern for abstraction that can allow you to give the power and stability of Airflow to users without forcing them to gain a deep understanding of the system.
Keep in mind that this implementation is meant to be illustrative of the pattern but is in no way complete for production. A good exercise would be to take the example code associated with this chapter and experiment with methods for authoring workflows with different levels of complexity, more functionality, alerts for the submitting QA engineer, and other Airflow operators entirely.
Be wary as you experiment with or adopt this pattern – taken to the extreme, you could find yourself attempting to define all of the capabilities in Airflow in a JSON object, which will only...
