Skip to content

Access control error after upgrading from version 2.9.3 to 2.10.0 #41540

@FelipeRamos-neuro

Description

@FelipeRamos-neuro

Apache Airflow version

Other Airflow 2 version (please specify below)

If "Other Airflow 2 version" selected, which one?

2.10.0

What happened?

After upgrading my Airflow deployment to the latest version, I noticed many DAG Import Errors mentioning access control

What you think should happen instead?

I have always created my dags with similar permissions such as these: {"EXAMPLE":["can_read","can_edit"]}, on access_control. Unless the documentation hasn't been updated yet, it should still work as intended.

How to reproduce

Deployment with Airflow 2.10.0 with Python 3.10 and with a dag created with similar access_control: {"EXAMPLE":["can_read","can_edit"]}

Operating System

Amazon Linux 2

Versions of Apache Airflow Providers

apache-airflow-providers-amazon==8.27.0
apache-airflow-providers-cncf-kubernetes==8.3.4
apache-airflow-providers-common-compat==1.1.0
apache-airflow-providers-common-io==1.4.0
apache-airflow-providers-common-sql==1.15.0
apache-airflow-providers-fab==1.2.2
apache-airflow-providers-ftp==3.10.1
apache-airflow-providers-http==4.12.0
apache-airflow-providers-imap==3.6.1
apache-airflow-providers-mysql==5.6.3
apache-airflow-providers-postgres==5.11.3
apache-airflow-providers-smtp==1.7.1
apache-airflow-providers-sqlite==3.8.2

Deployment

Official Apache Airflow Helm Chart

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:corearea:upgradeFacilitating migration to a newer version of Airflowkind:bugThis is a clearly a bugneeds-triagelabel for new issues that we didn't triage yet

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions