rgalex2034 opened a new issue, #12997: URL: https://github.com/apache/apisix/issues/12997
### Description ### Problem description We are using apisix with global configuration for a huge number of routes created by different teams. In this context, a global rate limit configuration plugin was deployed, but there are instances were this global configuration should be skipped in favor of a different, more permissive one. We know it's possible to remove the global configuration and make plugin configurations shared and referenced between routes, but we want to still preserve the global rule as a default, instead of relying on routes to attach to a plugin definition, because otherwise we can't enforce that. We came to a solution where we append special string on route names to be able to disable this global rate limit configuration on some routes, by using the _meta.filter property, and matching this special string on the $route_name variable. ### Feature request Having done this, it occurred to us that it may be useful to add metadata to a route, and be able to use it in the plugin's _meta.filter property, so we can share a common default behavior, but also skippable if requested. I wanted to discuss if it's a common case, enough to justify this as a new feature, or maybe I'm just guessing too much and there are different solutions to this problem. Thank you. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
