potiuk commented on issue #24742: URL: https://github.com/apache/airflow/issues/24742#issuecomment-1170825126
I think, personally, this problem is simply part of multi-tenancy in the future. I think for now custom security manager doing stuff in custom way is enough, because we have no concept of "team" and per-team acces. This is all implemented by a custom security manager if somoene wishes to do it (and yeah, it is complex and workaround). However, I think when/if we implement a "fully fledged" team managemenet and ownership concept in Airfow, we should definitely make it a case to handle. -- 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]
