GitHub user potiuk 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
> 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? As mentioned - I assume you are using Airflow 2, Airflow 3 uses different mechanisms for Dag processor and Dag bundle. And if you find similar issue in Airflow 3 - yes, it's absolutely worth to fix it - if only to help others who will start from Airflow 3 and for future you who will move to Airflow 3. > For the implementation itself, is the policy running before task run instead > of only when DAG processor is loaded expected? No idea. But if you will be fixing it, it's worth to take a deeper look and if the documentation is not clear enough - worth updating it - then in the PR to fix/improve things details might be discussed how it will behave in the futture. Generally Airflow 2 behaviour is - I said before - unlikely to change, we are only looking at fixing critical and security issues, so how it's working now is going to stay, I think. GitHub link: https://github.com/apache/airflow/discussions/53745#discussioncomment-13888640 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
