potiuk commented on issue #37456:
URL: https://github.com/apache/airflow/issues/37456#issuecomment-1961674622

   Please take a look at the logs (as Deployment Manager) and see what the 
detailed permission error says and report it here. For me it's not clear what 
documentaiton you are referring to, and what exactly is wrong, but I am sure we 
will all get more clarity when you provide some details from the logs and 
information explained there.
   
   It might be a bug in this case but it's not clear what permission is the 
problem - the log might be more verbose about it. Would also be great if you 
explain what are your high level expectations are. The model of ours is pretty 
fine grained and if you want to go into details and give detailed permissions 
it is expected from you that you understand in detail how airflow data model 
works 
(https://airflow.apache.org/docs/apache-airflow/stable/database-erd-ref.html) 
and what fine-grained permissions you should give. We are not providing more 
detailed documentation on that, it's up to you to deep dive if you chose to use 
such fine-grained permissions. I think in this case your user miss `dagrun` 
permission, but I am guessing - the logs should provide more information (and 
you should be able to figure it out from the model).
   
   Also as explained in other issues of yours - your expectations tha user who 
does not have permission will see more information is  misguided. In case of 
security and permission issues it's deliberate that as little information as 
possible is revealed and only Deployment Manager should be able to get more 
information by looking at the logs., Again - this is deliberate, designed like 
that and we are not going to change it. In this case security trumps 
convenience - you might have different expectations here, but we choose 
security over convenience.


-- 
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