potiuk commented on issue #29897: URL: https://github.com/apache/airflow/issues/29897#issuecomment-1970616571
No idea. If someone provide more details, mayb someone will look at it - not sure why tagging me would help here. Ideally - if someone adds more information and logs here, there is a chance somoene will diagnose and fix it. I think everyone's case is different - dpending on the conrete set of permissions and ways how their dags have permissions set the access might be possible or not. So describing more details about what permissions your users have, what permissions your roles have and what permissions your dags have, might help someone to solve the issues - note that we had recently a few security fixes that LIMITED permissions to dag imports because they were too broad. So I suggest to take a close look at your permissions and see if the user has the right set of permissions (and I cannot have an easy answer what permissions is the right set because if you have your own custom permissions and roles set (as was in the original issue) - it's up to you to build them in the way that makes sense for you. Also if you turn on debug logs - you might be able to see why the user cannot see the dag. So if you gather all the information, permission configuration and logs - it **might** help someone to investigate it Also - yes - there were some fixes since 2.6 to that, so its's likely 2.8.2 is more accurate about it - but if you have custom set of permissions, then you need to make sure they are as you expect them to have. -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
