API: add option to fetch only tags from ListInbounds#4870
API: add option to fetch only tags from ListInbounds#4870
Conversation
|
所以到底执着于输出一个tag列表做什么 而且还只有入站tag列表 |
It can be useful if you need fast and guaranteed delete user X from all inbounds. As I know, currently there is no method for "delete user with email X from all inbounds at once". So you need to know all TAGs of all inbounds which currently in core configuration. |
|
also we already have method ListOutbounds |
|
。。我懂了,你们有一个面板一样的东西。有人订阅到期了要移除他的用户信息,因为是商业面板所以包含了大量用户数据,打印入站配置会打印出非常大量的user信息出来,所以只能这样,到底了还是个机场面板功能。。。 |
yes, exactly. All user management is handled by Panel. In my case – Remnawave (I'm also maintainer of it :D). https://github.com/remnawave/panel Also, we have Typescript wrapper to gRPC API – https://github.com/remnawave/xtls-sdk Currently Remnawave Node (which handles Xray) is saving inbound tags from raw json config. It is okay, but if we use GRPC Core API, why there is no option just to get tags from core? |
|
@Fangliding could you approve it, pls? |
|
我的意见是至少为出站也添加这个功能 |
|
感谢! |
* feat: add new method for get only inbound tags from core. ListTags. * refactor: simplify creating response. * refactor: move getting tags in already exist method via option. (cherry picked from commit 486d005)
* feat: add new method for get only inbound tags from core. ListTags. * refactor: simplify creating response. * refactor: move getting tags in already exist method via option.
* feat: add new method for get only inbound tags from core. ListTags. * refactor: simplify creating response. * refactor: move getting tags in already exist method via option.
prev pr #4862