kesem0811 commented on PR #51814: URL: https://github.com/apache/airflow/pull/51814#issuecomment-2980173925
Just a quick thought β since Airflow 3.0+ always includes the DAG processor (itβs not optional anymore), do we really need this logic to dynamically enable or disable it? Would it make more sense to just set dagProcessor.enabled: true by default in values.yaml for Airflow 3.x+? That way, we can simplify the template by removing the version-based conditions β since the DAG processor is always active anyway. Let me know what you think β just trying to reduce complexity if it's safe to do so. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
