Yeah I’m with Jarek here. When someone offers a community provider they’re basically asking us to take care of it in perpetuity. This is fine as we want to ensure a good experience to users, but it also sets a high bar of “is this critical enough for us to maintain forever.”
FWIW this was one of the big reasons we created providers in the first place. To allow the external community to offer their own providers without going through us 🙂 On Fri, Dec 27, 2024 at 3:16 PM Jarek Potiuk <ja...@potiuk.com> wrote: > Why do you think it's better to add it as a community provider than > releasing it on your own ? Ansible is pretty popular - but some might say > "dated", and when we are committing to maintain something in the community > we tend to look in the future, rather than in the past. Why not release it > on your own and add an entry in > > https://airflow.apache.org/ecosystem/#third-party-airflow-plugins-and-providers > ? > > J. > > > On Fri, Dec 27, 2024 at 6:48 AM zheng liu <liuzheng...@gmail.com> wrote: > > > Hello Airflow Developers, > > > > As issue <https://github.com/apache/airflow/issues/45203> I mentioned, > I'm > > try to provide an ansible provider, in my work, it's > > works really well, and replaced the AWX for my daily operations. > > > > I'm already initiated a Pull Request, however we need to fix a few bits > and > > add System tests, so not yet ready for a full review. > > > > Please let me know if you accept this provider so that we can move on > with > > the PR <https://github.com/apache/airflow/pull/45204>. > > > > > > > -------------------------------------------------------------------------------------- > > Zheng Liu > > > > http://liuzheng.github.com > > >
