liuxiran commented on issue #431: URL: https://github.com/apache/apisix-dashboard/issues/431#issuecomment-683785047
> k8s supports tag too, so I think APISIX supports tag is easy:) Thanks, Ming Wen Twitter: _WenMing liuxiran <notificati...@github.com> 于2020年8月31日周一 下午4:44写道： > […](#) > @liuxiran <https://github.com/liuxiran> cool, that will be very useful for hundreds of routes. How about add tag for route, service? which is more flexible, a route can have multiple tags tag would be a more flexible and more fine-grained solution, user can it`s also useful for other modules like upstream and so on. And above tag, group would be closer to management, especially when there many users of different roles(dashboard could not have users only with one role), and many projects in this gateway, group would conveniently help us complete the division of route permissions. In fact, group + tag would be more perfectly， but tag may heavly reliance on database，as you have plane to replace the mysql，I think group may go first... — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <[#431 (comment)](https://github.com/apache/apisix-dashboard/issues/431#issuecomment-683650265)>, or unsubscribe <https://github.com/notificatio ns/unsubscribe-auth/AGJZBK635TFDDZ2N45FN7LLSDNPF5ANCNFSM4QQDJJTA> . wow~ It would be better that APISIX can supports tag~!! At the same time, we commit prs which enable apisix-dashboard to support group. BTW If you plan to add tag functionality to APISIX, my partners and I would like to contribute to it :) ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
