插件相关界面添加 "已启用" 分组选项，Insert new ButtonGroup component which with `All` , `Enabled` Child items in Plugin List View.

[inickel]

Feature request

• Route > Route List > Create or Configure > STEP 3 Plugin Config
• Service > Create Service > Step 2 Plugin
• Plugin > Plugin List > Enable > Global Plugin List

Please describe your feature

Insert new ButtonGroup(or Tabs) component which with All , Enabled child items.

When child item is selected Plugin List shows the results by filter all or enabled plugins

界面上添加一个按钮组或者选项卡组，选项为 默认选中 全部 和已启用 ，快速区分已经启用的插件功能。

Describe the solution you'd like

Describe alternatives you've considered

Additional context

有没有计划做一个类似 插件市场 的功能? 或者在线添加一个插件。

[zaunist]

Hi, @inickel . If you have any idea, welcome to send eamil to dev-subscribe@apisix.apache.org and follow the reply to subscribe mailing list, and you can send your idea to mailing list to discuss with other community members.

[juzhiyuan]

在线添加一个插件

Hi @inickel, this is a big and new feature for both Dashboard and Apache APISIX, when users upload a plugin (Lua or other languages), Dashboard should be able to send the Plugin to APISIX and reload it. Could you please send a DISCUSS to our mailing list first?

[Wcdaren]

Perhaps this problem is caused by the confusing logic of adding and enabling plugins, which we can solve with the following modifications.

• Form to show all added plugins (both enabled and unenabled)
• The logic of enabling plugins is modified to add plugins

[guoqqqi]

Hello @Wcdaren I have a few questions about your proposal

1. Form to show all added plugins (both enabled and unenabled)

I understand that you are thinking that when we configure a plugin and it is not enabled, it should also be displayed in the list, right? But right now we don't support this and I'm not sure if we need to change the API interface. The current implementation is that the plugin is removed when we don't enable it, and doesn't save its configuration, which is an area that could be optimised.

2. The logic of enabling plugins is modified to add plugins

I think adding is more like adding a new plugin, where the expression I think would be more appropriate to enable the functionality of a particular plugin.

[Wcdaren]

Of course, it can be tricky to make changes to the logic that distinguishes between add and enable. We can now solve this issue simply by sorting (enabling or not) as follows

[Morakes]

I think this might be helpful. 1.Add a plugin remote search to the plugin list to help us find the "enable" plugin quickly. Also, it might be clearer to change the "Add" button to the "Enable" button. Like this.

2.Add "Tab" to the global plugins to distinguish between "enable" and "not enbale", which looks intuitive.