jedcunningham commented on issue #47412: URL: https://github.com/apache/airflow/issues/47412#issuecomment-2702218268
> Ok, so the UI will assume a user can access any general page and if they don't have "read" permissions the list may be truncated or just empty. Is that right? Idk, feels not great to show variables anything, for example, if you don't have access to do anything with variables at all. The menu perms we need to expose in the auth manager will probably help here though, meaning if someone did land on the page via direct link or something, "empty" would be fine. > So would some entity id (dag_id, asset.id, etc) lookup work? I think that would work well for dag and asset details pages. But for our custom list pages, we might need to add permissions to the existing query. Ex: get /ui/dags could include if each dag can be triggered. We could add the ability to do that, yes. Doing it by entity id, or list of entity ids, is probably easier than doing something en mass like in the description. And baking those into certain responses so there isnt another round trip makes sense. -- 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]
