vincbeck commented on issue #57966: URL: https://github.com/apache/airflow/issues/57966#issuecomment-3576528457
> > he downside of this solution is we need to create many new endpoints, even though the implementation of these endpoints would be pretty thin. [@pierrejeambrun](https://github.com/pierrejeambrun) > > Interesting. I think we definitely need a way to call the backend to know if we have permissions or not to achieve something. > > I'm not a big fan of having a multitude of option endpoints to get those permissions but this makes me think of something related. > > To what extend is that possible to have a `meta permission endpoint`, that accept a list of permissions object and returns true/false for each of them. > > Example, we can pass `[(method, access_entity, entity_id), ...]`, i.e `[(POST, DagAccessEntity.RUN, test_id)]`, to know if I can trigger this dag. If in the same page I can also update a RUN, I can pass alongside the `[(POST, DagAccessEntity.RUN, test_id), (PUT, DagAccessEntity.RUN, run_id)]`. > > We can refine the structure, but that's the idea. Yep I am fine with that too. -- 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]
