eladkal commented on PR #54677: URL: https://github.com/apache/airflow/pull/54677#issuecomment-3218297869
> UI Alerts are helpful for a variety of reasons, but in the current Airflow 3 implementation, they are strictly static for the entire lifetime of the webserver/api-server. Therefore, updates to UI alerts require code changes and special automation or manual rollouts/restarts when alerts must change. This is very good if we can do that! It's not just in Airflow 3. @pierrejeambrun The use case of such capability is for announcing something in large dag author deployments. For example: "We have issues with K8s cluster, task may be delayed no need to contact cluster admins". @codecae I think this feature needs some explanation in the UI alert docs about how to make it dynamic https://github.com/apache/airflow/blob/18690f7babce185a2aa456452c6acee41fa7b77c/airflow-core/docs/howto/customize-ui.rst#L65 -- 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]
