mik-laj commented on issue #11728: URL: https://github.com/apache/airflow/issues/11728#issuecomment-717484972
@ryw The API only partially solves. this problem. Solves case 1 and 2 because the API does not have any options that are unique to certain executors. In this case, the "run" option only works with Celery and Kubernetes and has no effect on any other, so it was not implemented. > 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 So if we rewrite the UI, we have to delete these options or add endpoints. For cases 3 and 4, the API has no influence. It's just that the API uses the same code, so it communicates with other components anyway. ---------------------------------------------------------------- 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]
