Sure - there is the documentation you should browse https://airflow.apache.org/ and airflow use cases are described here: https://airflow.apache.org/use-cases/. You can find a lot of information in Concepts https://airflow.apache.org/docs/stable/concepts.html#
Your questions are a lot about security and permissions - you should study Security for that https://airflow.apache.org/docs/stable/security.html Quick answer (but It is based on quick understanding) of what you mean: > • 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. >> > Not possible • Allow users to define authorization at task level. >> > Yes. Read about Connections https://airflow.apache.org/docs/stable/concepts.html#connections • Add a new permission to control who can zoom into a sub-dag. >> > I think so (depends how you define ti) - we have https://airflow.apache.org/docs/stable/security.html#rbac-ui-security and you will need to try it out to see if it fits your needs. • Allow users do define permissions on custom Operator attributes. >> > Not sure what you mean. Permissions (RBAC) are only available on the UI side not DAG definition so likely no. > • 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 >> ). >> >> > If they don't fall into current ones (which are pretty flexible) - no. > >> > 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? >> > It's a community-driven effort - it's impossible to say "how hard" it is and how much "effort" is needed. If something is not on a general roadmap for 2.0 https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+2.0 (and someone is already working on it) and you would like to add some new features to airflow you can either try to add it on your own (you are most welcome to contribute) or find someone who can work on such changes - but beware since this is a product used by many, any fundamental changes usually take a lot of time and discussion to implement. > >> Please feel free to redirect me to a different forum, in case this isn't >> the place for such questions. >> >> Thanks, >> Kislaya >> > -- Jarek Potiuk Polidea <https://www.polidea.com/> | Principal Software Engineer M: +48 660 796 129 <+48660796129> [image: Polidea] <https://www.polidea.com/>
