GitHub user adrian-edbert added a comment to the discussion: DAG Cluster Policies check running during task run with different relative_fileloc value than when it's run by DAG processor
Thanks for the reply and confirmation, will do the check on the how it works on Airflow 3 and make PR if possible We do use the DAG bundles, with the assumption that the relative_fileloc will always be pointing to the relative file location based on the dag bundle storage path Understood that we are doing "multi-tenancy" which is not natively supported, I believe what we trying to achieve is more like the option C mentioned on in the [AIP-67](https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-67+Multi-team+deployment+of+Airflow+components) where we tried to use cluster policies to enforce some DAG rules based on the folder, this is not ideal and we hope to migrate to the ways that more fit to AIP-67 later I do have some follow up question regarding this if you don't mind - The workaround is pretty easy as you mentioned, we add some rule to check if relative_fileloc value is the same value as fileloc and skip the check entirely if so, and regarding the AIP-67 will change how this works, do you think still worth it to open a PR to address this issue? - For the implementation itself, is the policy running before task run instead of only when DAG processor is loaded expected? GitHub link: https://github.com/apache/airflow/discussions/53745#discussioncomment-13887548 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
