mik-laj edited a comment on pull request #14664: URL: https://github.com/apache/airflow/pull/14664#issuecomment-796741070
> These endpoints are similar to what you would see when you go to Security > List Roles on the webserver. So it will work properly with any auth type since it just reads DB roles and permissions which are part of airflow. That's what I understand, unless I'm missing something. What do you think? This is very confusing to end users. They don't know all the limitations we have in the project. A similar situation occurs when the user uses the Backend Secret. See: https://apache-airflow.slack.com/archives/CCR6P6JRL/p1615394435242400 We should think about how to limit similar surprises because it takes users hours/days to discover that everything works as intended, but they misunderstood our product. This was one of the reasons this endpoint did not appear in the first version of the API. > # API for optional components > > The goal is not to develop an API for non-fundamental components. There are expectations to develop an API that provides additional features. For example: > > allows access to node information when using CeleryExecutor, > for deeper integration between Airflow and Kubernetes when KubernetesExecutor is used > for monitoring > Integration with these components will be covered in other documents. https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-32%3A+Airflow+REST+API As the simplest solution, we can disable this endpoint if it doesn't work properly in a current configuration, but we can also write a smart solution. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
