I didn't get the exact problem if you store them in the swagger against each path like you did previously. We can add a new property for each operation "arn" and then update the swagger using that during API creation, update? We can modify the APIM swagger parsers to do that conversion vise versa. Thanks!
On Thu, Sep 19, 2019 at 11:18 AM Binod Karunanayake <bi...@wso2.com> wrote: > Hi all, > > I recently noticed the following changes due to migrating from 2.6 to 3.0 > > - *apiDefinition is no longer passed by the JSON object which is > passed at the API creation time (before apiDefinition was passed as a JSON > string).* > - *APIDefinitionFromOpenAPISpec class is deprecated.* > - *new property 'operations' is introduced to the JSON object which is > passed at the API creation time.* > > Because of these changes, I cannot pass the ARNs in apiDefinition per > resource and I have to modify the code to set ARNs to resources. Also, as I > need to implement this AWS Lambda feature to the micro gateway it'll be > better if I could add ARN property to the swagger definition per resource. > Not only that I need to add 2 key values to *endpointConfig. *However, > this new properties will not be used in other API types apart from the > lambda use case. > > *Note that those Keys and ARNs should be read in velocity_template.xml > also*. I think it's better to do a swagger update during runtime. As this > feature should be available in the micro gateway, adding extensions to > swagger will be useful. > > Or please suggest me a way to store Keys and ARNs. > > Thanks. > -- > *Binod Karunanayake* | Software Engineering Intern | WSO2 Inc. > (m) +94716611642 | (e) bi...@wso2.com > [image: http://wso2.com/signature] <http://wso2.com/signature> > -- Malintha Amarasinghe *WSO2, Inc. - lean | enterprise | middleware* http://wso2.com/ Mobile : +94 712383306
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
