# #region AlembicEnvModule [C:3] [TYPE Module] [SEMANTICS alembic, migration, env, logging] # @BRIEF Alembic environment configuration — sets up DB connection, model metadata, # and logging. Contains ADR [LOG-001] for suppress_existing_loggers=False. # @LAYER Infrastructure # @RELATION DEPENDS_ON -> [LoggerModule] # @INVARIANT fileConfig() must be called with disable_existing_loggers=False # to prevent disabling superset_tools_app logger (see ADR LOG-001). # #endregion AlembicEnvModule from logging.config import fileConfig import os from pathlib import Path import sys from sqlalchemy import engine_from_config, pool from alembic import context # Ensure backend/src is importable sys.path.insert(0, str(Path(__file__).resolve().parents[1])) # this is the Alembic Config object, which provides # access to the values within the .ini file in use. config = context.config # Allow overriding sqlalchemy.url via DATABASE_URL env var if "DATABASE_URL" in os.environ: config.set_main_option("sqlalchemy.url", os.environ["DATABASE_URL"]) # Interpret the config file for Python logging. # This line sets up loggers basically. # @ADR [LOG-001] disable_existing_loggers=False # @RATIONALE Python 3.13's logging.config.fileConfig() defaults to # disable_existing_loggers=True, which sets logger.disabled = True on ALL # existing loggers not listed in alembic.ini's [loggers] section. This # includes our 'superset_tools_app' and 'cot' loggers. With disabled=True, # Logger.isEnabledFor() immediately returns False (see Python 3.13 source), # silently dropping every logger.info()/warning()/error() call across the # entire application. The SS-TOOLS logging system manages its own handlers # via configure_logger() — Alembic's INI-based config is irrelevant here. # @REJECTED Adding superset_tools_app to alembic.ini [loggers] was rejected # because it couples app logging config to Alembic's ini format, which is # fragile and non-obvious for future maintainers. if config.config_file_name is not None: fileConfig(config.config_file_name, disable_existing_loggers=False) # add your model's MetaData object here # for 'autogenerate' support # Import ALL model modules so their tables are registered in Base.metadata from src.models import ( # noqa: F401, E402 agent, api_key, assistant, auth, clean_release, dashboard, dataset_review_pkg, filter_state, git, llm, maintenance, profile, report, storage, task, translate, ) # Import config models with explicit alias to avoid name collision with alembic config import src.models.config as models_config # noqa: F401, E402 from src.models.mapping import Base # noqa: E402 target_metadata = Base.metadata # other values from the config, defined by the needs of env.py, # can be acquired: # my_important_option = config.get_main_option("my_important_option") # ... etc. def run_migrations_offline() -> None: """Run migrations in 'offline' mode. This configures the context with just a URL and not an Engine, though an Engine is acceptable here as well. By skipping the Engine creation we don't even need a DBAPI to be available. Calls to context.execute() here emit the given string to the script output. """ url = config.get_main_option("sqlalchemy.url") context.configure( url=url, target_metadata=target_metadata, literal_binds=True, dialect_opts={"paramstyle": "named"}, ) with context.begin_transaction(): context.run_migrations() def run_migrations_online() -> None: """Run migrations in 'online' mode. In this scenario we need to create an Engine and associate a connection with the context. """ connectable = engine_from_config( config.get_section(config.config_ini_section, {}), prefix="sqlalchemy.", poolclass=pool.NullPool, ) with connectable.connect() as connection: context.configure( connection=connection, target_metadata=target_metadata ) with context.begin_transaction(): context.run_migrations() if context.is_offline_mode(): run_migrations_offline() else: run_migrations_online()