If any of these can be self-understood, can someone please guide me? It would be really helpful!
Thanks, Kislaya On Mon, Mar 2, 2020 at 3:14 PM Kislaya Ranjan <[email protected]> wrote: > Hi All, > > I am working on a project which has a lot of overlap with Airflow. In > order to avoid reinventing the wheel, my team wants to evaluate if we can > build on top of Airflow or tweak it to solve our use cases. > > Some of the requirements are: > • Allow users to extend states and map custom states to system-understood > states. eg. Users could define states run_0, run_50, run_100, where run_100 > = success. > • Allow users to define authorization at task level. > • Add a new permission to control who can zoom into a sub-dag. > • Allow users do define permissions on custom Operator attributes. > • Allow users to define custom trigger rules dynamically (without > requiring them to tweak/extend the class: > https://github.com/apache/airflow/blob/97a429f9d0cf740c5698060ad55f11e93cb57b55/airflow/utils/trigger_rule.py > ). > > Can you please help me understand the following, per requirement: > - Can I readily achieve it using Airflow? If yes, how do I go about it? > - How much effort is required to achieve it? > > Please feel free to redirect me to a different forum, in case this isn't > the place for such questions. > > Thanks, > Kislaya >
