refactor: move vendored Flask writer to framework/flask_app_config_writer

Renames the vendored writer back to its upstream name and groups it under a
`framework` module (mirroring the convention in trino-operator), signalling it
as vendored code that is a candidate for a shared crate. The same writer is
still used by superset-operator via the product-config crate. No behaviour
change; the writer body is unchanged from the crate source.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: adwk67

rust/operator-binary/src/airflow_controller.rs

@@ -92,7 +92,7 @@ use crate::{
         v1alpha2,
     },
     env_vars::{self, build_airflow_template_envs},
-    flask_config_writer::{self, FlaskAppConfigWriterError},
+    framework::flask_app_config_writer::{self, FlaskAppConfigWriterError},
     operations::{
         graceful_shutdown::{
             add_airflow_graceful_shutdown_config, add_executor_graceful_shutdown_config,
@@ -754,7 +754,7 @@ fn build_rolegroup_config_map(
 
     let temp_file_footer: Option<String> = config.remove(CONFIG_OVERRIDE_FILE_FOOTER_KEY);
 
-    flask_config_writer::write::<AirflowConfigOptions, _, _>(
+    flask_app_config_writer::write::<AirflowConfigOptions, _, _>(
         &mut config_file,
         config.iter(),
         PYTHON_IMPORTS,

rust/operator-binary/src/crd/mod.rs

@@ -55,7 +55,7 @@ use crate::{
             CeleryBrokerConnection, CeleryResultBackendConnection, MetadataDatabaseConnection,
         },
     },
-    flask_config_writer::{FlaskAppConfigOptions, PythonType},
+    framework::flask_app_config_writer::{FlaskAppConfigOptions, PythonType},
     util::role_service_name,
 };
 

rust/operator-binary/src/framework.rs

@@ -0,0 +1,8 @@
+//! Local helpers vendored from upstream crates, grouped here as candidates for a
+//! future shared home (e.g. operator-rs) once one exists.
+//!
+//! Mirrors the `framework` module convention used by other Stackable operators
+//! (e.g. trino-operator) for code that is intentionally duplicated until it can
+//! be upstreamed.
+
+pub mod flask_app_config_writer;

…erator-binary/src/flask_config_writer.rs …src/framework/flask_app_config_writer.rsrust/operator-binary/src/flask_config_writer.rs renamed to rust/operator-binary/src/framework/flask_app_config_writer.rs rust/operator-binary/src/flask_config_writer.rs renamed to rust/operator-binary/src/framework/flask_app_config_writer.rs

@@ -1,14 +1,20 @@
 //! Writer for Flask App configurations (Python config files).
 //!
-//! Vendored from `product_config::flask_app_config_writer` so airflow-operator can
-//! drop the `product-config` crate dependency. Applications based on the Flask App
-//! Builder (e.g. Apache Airflow) use configuration files written in Python. This
-//! writer only covers top-level assignments of a few primitive types and
-//! expressions — it is not a general Python code generator.
+//! Vendored verbatim from `product_config::flask_app_config_writer` so
+//! airflow-operator can drop the `product-config` crate dependency. Applications
+//! based on the Flask App Builder (e.g. Apache Airflow, Apache Superset) use
+//! configuration files written in Python. This writer only covers top-level
+//! assignments of a few primitive types and expressions — it is not a general
+//! Python code generator.
 //!
 //! Primitive types are escaped accordingly. Python expressions are written as-is;
 //! invalid expressions produce invalid configuration files. Config overrides that do
 //! not map to a known option are treated as plain expressions.
+//!
+// TODO: This is vendored, not airflow-specific. superset-operator still depends on
+// `product_config::flask_app_config_writer`; this writer is a candidate for a shared
+// crate (e.g. operator-rs) so both operators can drop the product-config crate.
+// Until such a home exists it is duplicated here, kept identical to the upstream source.
 
 use std::{
     io::{self, Write},

rust/operator-binary/src/main.rs

@@ -44,7 +44,7 @@ mod controller;
 mod controller_commons;
 mod crd;
 mod env_vars;
-mod flask_config_writer;
+mod framework;
 mod operations;
 mod product_logging;
 mod service;