Access request/response body in overrides

alexkarcher-msft commented 7 years ago

As a part of first-class JSON support, we should add the ability for Proxies to override specific parts of the request/response body. The current behavior is and all or nothing override of the body.

alexkarcher-msft commented 6 years ago

Linking this up to a uservoice item. Notable that we don't have support to override the request body at all. https://feedback.azure.com/forums/355860-azure-functions/suggestions/32948629-proxies-should-support-backend-request-body-expres

anthonychu commented 6 years ago

Public link to uservoice item: https://feedback.azure.com/forums/355860-azure-functions/suggestions/32948629-proxies-should-support-backend-request-body-expres

alexkarcher-msft commented 6 years ago

Thanks @anthonychu ! You're the glue holding this community together!

CharlieDigital commented 3 years ago

Hi, chiming in on this old issue.

I have recently had the "pleasure" of using AWS AppSync. I use quotes because while it is supremely powerful, it can also be quite cumbersome to use in practice due to the need to learn Apache Velocity Template Language (VTL) and the lack of good tooling support in my opinion.

That power comes from the ability to arbitrarily transform proxied requests and response in both directions using VTL.

You can easily see why this is tremendously powerful because it becomes a true unifying gateway that can fulfill a ton of use cases with very little code (if we do not consider VTL templates as code). For example:

Legacy Integration. The ability to proxy and transform an incoming request to a legacy backend format and then from the legacy backend response to the expected format.
Direct DB Path. It is possible to transform incoming requests from the front-end into queries against DynamoDB without any code in between. This is actually amazing because there is zero cold start issues when connecting a FE to DynamoDB using this mechanism
Data Shaping. The ability to implement rudimentary logic in VTL to shape the data in both directions for security, for size, for whatever

Leaving aside the GQL aspect of AppSync for a moment, as far as I am aware, there is no analog to AppSync on Azure today.

Would love to see some pathway towards this capability in Azure as it would make building certain scenarios on Functions much more straightforward and performant (namely legacy API integration and Fowler's "Strangler Fig" pattern).

Azure / azure-functions-host

Access request/response body in overrides #1968