[GitHub] [airflow] potiuk commented on issue #24742: Import errors thrown by *new* DAGs are hidden from RBAC users' web ui
potiuk commented on issue #24742: URL: https://github.com/apache/airflow/issues/24742#issuecomment-1313033873 The answer is pretty much always the same - It will be implemented, when someone implements it. This is how open-source software works. If somone badly needs a feature in OSS project, and no-one is actually doing it, then they can do various things: * implement them * find somene who implements it * them or they company can sponsor somoene who migh take an interest in it * wait until someone implements it * implement it in they own fork and possibly contribute it back * you (or someone from your company - or even paid by your company) can start a discussion in the devlist and explain why you need it and (in case of this problem goes really deep into the core of Airflow it likely will require someone to come up with idaes how to do what you want, discuss and get it to conclusion (and eventually likely voting on AIP - Airflow Improvement Proposal). I think following those are some of the ways you can make those things progress. -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #24742: Import errors thrown by *new* DAGs are hidden from RBAC users' web ui
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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
