Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contribution Guide (https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our pre-commits will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: [email protected]
  Slack: https://s.apache.org/airflow-slack

Do not use WARN. Use WARNING instead. If we agree to do this.

Yeah, I think that's a more complete solution, and would certainly resolve this for me.

What about setting up logging_config_class before running alembic commands and not touching logs with alembic at all? That way we could use the existing logging override mechanism to do what we want with the alembic logs.

Currently the alembic logging configuration are loaded from this file without any possibility to update them:

airflow/airflow/utils/db.py

Line 728 in 73e0313

config = Config(os.path.join(package_dir, "alembic.ini"))

I think it might be a good feature if we add a new Airflow configuration to provide a custom ini file for alembic, then you can update it as you like in your Airflow server. WDYT?

Agree with @hussein-awala - being able to specify alembic.ini would be much better.

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions.

the issue was closed by #31415