Sorry for replying late, we have finally done and closed this ticket today. It takes a long time, because I am busy with other stuff, and no one in our community is interested in this issue.
The result is we remove the ambari plugin in [1], and we create a new repository in [2]. Anyone who is interested in the ambari plugin and wants to support DolphinScheduler 2.0 is encouraged and we love to see this. You could submit PR to [2]. [1]: https://github.com/apache/dolphinscheduler/pull/7880 [2]: https://github.com/apache/dolphinscheduler-ambari On 2021/11/19 06:44:57 Jiajie Zhong wrote: > Hey guys, > > I am here to proposal we DolphinScheduler remove Apache Ambari plugin in > our main repo. > > I think we should keep our main repo as pure as possible, and Ambari plugin > is not our major features. > > For now Ambari plugin in our main repo, we have to verify the availability > when we create a new release. > And some users would create an issue about the plugin. All this things I > think is not the responsibilities of > DolphinScheduler, it more looks like the responsibilities of > DolphinScheduler, and should not blame > DolphinScheduler core itself. > > Maybe it is time to make it clear whose responsibility it is. > > If this proposal passes, we should: > 1. Create an issue and PR to remove code in `ambari_plugin` and other > related in main repo > 2. Remove related document in dev and 2.0 > > Best Wish > — Jiajie >
