FelipeRamos-neuro opened a new issue, #41540:
URL: https://github.com/apache/airflow/issues/41540

   ### 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
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to