zach-overflow commented on issue #51971: URL: https://github.com/apache/airflow/issues/51971#issuecomment-3006466154
Thank you @vincbeck, this is a super helpful summary and very much appreciated! > > Which API-action + resource combinations are possible or not, especially as it relates to DAG sub-entities. (I was only able to understand some of these expected action-resource combinations by digging through the various files under airflow.api_fastapi.core_api.routes.public, but it feels risky to base my assumptions on code which may not be part of the public interface) > Can you provide concrete example of what you might think as a combination does not makes sense? It might be simpler to answer that way :) Funny enough, the example I was going to give was related to a `DELETE` operation on a DAG Run resource, and what that translates to for the DAG resource itself, but the rest of your answer helped clarify this. Glad to hear the `airflow.security.permission` module is not recommended, as I was concerned whether I was going down the wrong path with my auth manager implementation. Likewise, I was curious about the `MENU` API action. To that end, I agree the `MENU` method might make sense to drop from the list given the `filter_authorized_menu_items` I'll be trying to wrap up some work on my end and then I think once I've got some free time in the next week or so I can help draft up some documentation updates for the auth manager. Thanks again for clarifying this. Super helpful! -- 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
