bisakhmondal commented on issue #5485: URL: https://github.com/apache/apisix/issues/5485#issuecomment-966400503
> So the request is terminated by APISIX and won't be proxied to the upstream, if we use this plugin? Yes, @tokers, the serverless function URI will be treated as a new upstream. Is there any use cases when we need both conventional upstream and serverless functions as upstream-duo? > Is it more suitable to extend the Upstream so that these serverless platforms can be supported as the standard backends. The idea is really good. But I am not sure considering this massive refactoring if the benefits that come after that would be a good tradeoff. Because, at the end of the day, we need to handle framework-specific authorization. That's where we again have to introduce plugins. They not only vary in header names for authorization but also some of the providers support complex authz techniques such as (aws key-secret pair, IAM role-based authz etc). So I think we can't abstract this plugin requirement into a single entity. Let me know what do you think, definitely it's going to be a good discussion : ) Thanks! -- 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]
