Keep a TODO for the task handler log level

The comment now separates the two things: the airflow.task logger level can
already be overridden through the CRD, and the task handler level still cannot.
The TODO points at issue 650 and notes it needs a new field in
AutomaticContainerLogConfig in operator-rs.

Author: Churi12

CHANGELOG.md

@@ -9,9 +9,10 @@
 - The RBAC ServiceAccount and RoleBinding are now built with the operator-rs `v2::rbac`
   functions and carry the full set of recommended labels ([#821]).
 - Bump stackable-operator to 0.114.0 ([#827]).
-- Removed a stale comment suggesting the airflow.task logger level could not be
-  overridden through the CRD. It already can, by adding a loggers entry for
-  airflow.task. Added regression tests for this ([#829]).
+- Documented that the airflow.task logger level can already be overridden through the
+  CRD by adding a `loggers` entry for `airflow.task`, and added regression tests that
+  pin the ordering this relies on. The task *handler* level is still not configurable
+  ([#829]).
 
 [#814]: https://github.com/stackabletech/airflow-operator/pull/814
 [#821]: https://github.com/stackabletech/airflow-operator/pull/821

rust/operator-binary/src/controller/build/properties/product_logging/mod.rs

@@ -97,10 +97,16 @@ for logger_name, logger_config in LOGGING_CONFIG['loggers'].items():
     if logger_name != 'airflow.task':
         logger_config['propagate'] = True
     # The default behavior of airflow is to enforce log level 'INFO' on tasks. (https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html#logging-level)
-    # This can be overridden through the CRD by adding an entry for the logger
-    # name 'airflow.task' under loggers, since the code appended further below
-    # (loggers_config) runs after this block and reassigns the level for any
-    # logger explicitly listed in the CRD.
+    # The level of the airflow.task LOGGER can be overridden through the CRD by
+    # adding an entry for the logger name 'airflow.task' under loggers, since the
+    # code appended further below (loggers_config) runs after this block and
+    # reassigns the level for any logger explicitly listed in the CRD.
+    # TODO: Make the task HANDLER log level configurable through the CRD with
+    # default 'INFO', so that a different level can be sent to the UI than to the
+    # file and Vector appenders. This needs a new field in
+    # AutomaticContainerLogConfig in operator-rs, see
+    # https://github.com/stackabletech/airflow-operator/issues/650
+    # e.g. LOGGING_CONFIG['handlers']['task']['level'] = {{task_log_level}}
     if 'handlers' in logger_config and 'task' in logger_config['handlers']:
         logger_config['level'] = logging.INFO