ahipp13 opened a new issue, #35177:
URL: https://github.com/apache/airflow/issues/35177
### Apache Airflow version
Other Airflow 2 version (please specify below)
### What happened
So I am on Airflow 2.6.3, and we ran into a weird bug that I am wondering if
it has been seen or addressed.
We are running Airflow 2.6.3 on Kubernetes using the official Airflow Helm
Chart. We have a Git Sync Sidecar to hold our DAGs, and we currently have 2
teams in our Airflow instance, so we use 2 separate Roles so that they can only
see the DAGs that belong to their team. To accomplish this we have each team
but a statement like this in their DAG statements:
access_control={'ROLE_NAME': ['can_edit', 'can_read']},
What happened was one of the teams pushed a DAG for the first time to the
Git Sync Sidecar, and it had an import error. But, the team could not see the
import error. Only I could see it, because I have the "User" role. With their
team role, they could not see the import error, so it looked like the DAG was
not in Airflow yet.
### What you think should happen instead
The import error should still show up to the people that have the role to
see the DAG. The access control execution in a DAG should still run even if
their is an import error
### How to reproduce
Create a new DAG that has yet to be uploaded to a Git Sync Sidecar. Create a
new role for this DAG, and then in the new DAG reference the new role and give
it edit and read permissions like I said above. Then, make sure the new DAG has
an import error and upload it to the git sync sidecar.
### Operating System
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
### Versions of Apache Airflow Providers
apache-airflow-providers-apache-kafka==1.2.0
apache-airflow-providers-cncf-kubernetes==7.7.0
apache-airflow-providers-common-sql==1.5.2
apache-airflow-providers-ftp==3.4.2
apache-airflow-providers-http==4.4.2
apache-airflow-providers-imap==3.2.2
apache-airflow-providers-microsoft-azure==8.0.0
apache-airflow-providers-postgres==5.7.1
apache-airflow-providers-smtp==1.4.0
apache-airflow-providers-sqlite==3.4.2
### Deployment
Official Apache Airflow Helm Chart
### Deployment details
Deploying to kubernetes using the helm and the official airflow helm chart.
### Anything else
We have only seen this problem happen to us once, so it is not a very common
problem. That is why I want to report it to see if this has been solved or if
anyone is aware about it. I will try my best to dig in and see if I can fix but
wanted to get this out there so other people can dig in as well. Please let me
know if this has been solved in a newer airflow version.
### 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: commits-unsubscr...@airflow.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
