aaron-wolmutt commented on issue #57966: URL: https://github.com/apache/airflow/issues/57966#issuecomment-3587735842
> Or maybe we could have one call where we can ask for multiple entity ids. We already have it implemented in some cases I believe (and keycloak client can efficiently ask for multiple resources - we looked at it before). I was thinking that the call would happen after login. So, the user authenticates, the /ui/auth/meta/permissions API is called, then an authorization object persisted to local storage. It doesn't have to be local storage or session storage; it could be a global state manager or object if one is available (for example Redux). The only downside would be page load time could be too slow if the Airflow has 100+ DAGs. In the case that the Airflow has 100+s of DAGs, I think calling the /ui/auth/meta/permissions API when the run DAG modal is opened might be better. I guess it depends on what we're considering best practices. -- 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]
