Yes, that's right.
If a user selects lambda as the endpoint, he'll be shown only the ARN
mapping in the resources page.
If a user first goes to the resources page without setting endpoint type,
he'll be shown normal http resources.
On Mon, Sep 2, 2019 at 12:14 PM Dushan Silva wrote:
> i'm +1
i'm +1 for it,
One thing I want to clarify is, when we follow this approach when a user
first visits the resources page (without adding lambda endpoint) he will be
shown the normal http resources right ? and when the user adds the endpoint
he will be shown the ARN stuff in the resources page? is
Hi all,
Considering suggested ideas I'm +1 for adding user role details in
endpoints page and ARNs in the resources page. Also, +1 for adding a wizard
for the first time users.
As @Kasun Thennakoon mentioned it'll be better if we
could list down the ARNs when the user sets user role
Hi All,
While I'm +1 to add a wizard for onboarding users to AWS backend APIs, but
I don't think we should add a separate menu for AWS backends, IMHO we can
have AWS related configurations in the endpoints section. and have the ARN
selection in resources page?
I think it will be convenient for
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
