potiuk commented on issue #59280: URL: https://github.com/apache/airflow/issues/59280#issuecomment-3638708813
I would say it might be a good part of Airflow Ecosystem - if someone would like to develop and maintain it - and publish outside of Airflow Community. I don't see particular reason why this should be developed here in the community - this should rather be driven by those who run grafana on their own and would make it "production proven". There are many tools and extensions to Airflow that our Ecosystem page has https://airflow.apache.org/ecosystem/ and if someone would like to publish their Grafana CLI there they are absolutely free to do so. We - in Airflow - focus on doing what we are best at - and for few years we follow "airflow as a platform" approach - i.e. what we can take out from Airlfow and let "others" build and extend airflow on top of APIs and features we expose. That one seems like ideal candidate for someone to build and publish. Sure. But I don't think as maintainers we would find time, energy and focus to maintain - especially that we are not Grafana specialits. Better to leave it to them I convert this issue to a discussion so that any discussion about it might be continued there. -- 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]
