ahipp13 commented on issue #29897: URL: https://github.com/apache/airflow/issues/29897#issuecomment-2260894175
> I am unable to replicate the behaviour in Airflow 2.5.1 or 2.6.3. In the original scenario, the custom role does not have the respective read on DAG permission. > > The role must have all the following to see import errors of the respective DAG the role can read. > > * can read on Website > * can read on DAG:<insert_dag_Id> > > A role with the following permissions can see ALL import errors. > > * can read on Website > * can read on DAGs > > I believe the permission `can read on ImportError` does not impact whether a user can see the import errors in Airflow 2.5.1 or 2.6.3. > > This is not true on Airflow 2.9.3. > > The role must have all the following to see import errors of the respective DAG the role can read. > > * can read on Website > * can read on ImportError > * can read on DAG:<insert_dag_Id> > > The role must have all the following to see import errors to see all import errors DAG. > > * can read on Website > * can read on ImportError > * can read on DAGs I am currently on 2.9.2, and this still exists. The reason being is because for one of my roles, the permission "can read on DAG:<insert_dag_Id>" is assigned inside the DAG itself. So if the DAG hasn't been uploaded yet, and it gets an ImportError, then that means it doesn't enter the UI, which means the permission "can read on DAG:<insert_dag_Id>" does not get assigned to the role, so they cannot see it. -- 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]
