Hi Binod,
Please create a feature request in [1] if your are planning make this
available on MGW.
[1]: https://github.com/wso2/product-microgateway/issues/new/choose
Thanks,
Praminda
On Fri, Aug 30, 2019 at 2:20 PM Binod Karunanayake wrote:
> Hi,
>
> @Himasha Guruge
>
> Is this capability
Hi Binod
On Fri, Aug 30, 2019 at 2:20 PM Binod Karunanayake wrote:
> Hi,
>
> @Himasha Guruge
>
> Is this capability going to be available in the micro gateway as well? In
> such a case could we introduce extensions to add lambda endpoints in the
> swagger too?
>
> 1. Yes, this feature will be
Hi,
@Himasha Guruge
Is this capability going to be available in the micro gateway as well? In
such a case could we introduce extensions to add lambda endpoints in the
swagger too?
1. Yes, this feature will be available in the micro gateway
2. I have introduced new extensions for aws lambda in
Hi all,
I feel like there two approaches we can take to this,
If we are going with disabling endpoints and resources, and only enabling
the aws lambda section then I think we might need to take the endpoint type
(either http or lambda at api creation time) so when the initial api is
created it
Hi Binod,
Is this capability going to be available in the micro gateway as well? In
such a case could we introduce extensions to add lambda endpoints in the
swagger too?
Thanks,
Himasha
On Fri, Aug 30, 2019 at 12:21 PM Chanaka Jayasena wrote:
> Also +1 to disable both Endpoints section and
Also +1 to disable both Endpoints section and Resources while enabling
the LAMBDA section as you suggested. Wizard is something you can do
optionally. But you can reuse the components from Resource and Endpoints to
build the LAMDA component.
thanks,
Chanaka
On Fri, Aug 30, 2019 at 12:07 PM
I would suggest to add them separately and provide them a wizard to set AWS
Lambda starting from the BIG overview page.
The wizard will take the user through necessary steps and guide him through
the different sections.
With old UI tech, it's difficult to do something like this without
Hi all,
So far, I have developed the code for creating apis to invoke Lambda
functions through REST API. *Still the above issue (set ByteBuffer response
to response path directly) is not resolved*. However, I'm planning to start
developing UI for this feature. Before that, I want to clarify some
