access control logs

[Shlomixg]

Apache Airflow version

2.7.1

What happened

After upgrading to 2.7.1 from 2.5.3 we encountered those logs in the scheduler logs:

[2023-09-11T05:52:34.865+0000] {logging_mixin.py:151} INFO - [2023-09-11T05:52:34.865+0000] {security.py:708} INFO - Not syncing DAG-level permissions for DAG 'DAG:<dag_name>' as access control is unset.

Since we have multiple DAGs for the same DAG file (>40), and the DAG processor is running on a high period, we have a lot of redundant logs, which creates more unnecessary data to store.

Adding the setting access_control={} did not change the logs.

We don't want to manage the access control for each DAG, as we have a high-level approach, but we also don't want these logs.

What you think should happen instead

Add some settings to allow avoid printing this info logs about sync permissions

How to reproduce

Airflow Version - 2.7.1
Python - 3.11.5

Create a DAg without setting access_control and watch logs. e.g. XXX/_data/scheduler/2023-09-11/dag_name.py.log

Operating System

Debian GNU/Linux 11 (bullseye)

Versions of Apache Airflow Providers

No response

Deployment

Docker-Compose

Deployment details

No response

Anything else

No response

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.

[potiuk]

Yeah. We shoudl change those logs about syncing to debug. For now a workaround is to use https://airflow.apache.org/docs/apache-airflow/stable/administration-and-deployment/logging-monitoring/advanced-logging-configuration.html and set airflow.www.security.AirflowSecurityManager logger level to WARNING.

[csp33]

I'll do it!

[potiuk]

Feel free.