On Thu, Oct 20, 2016 at 10:38 AM, Malintha Amarasinghe <[email protected]> wrote:
> > > On Thu, Oct 20, 2016 at 10:31 AM, Thilini Cooray <[email protected]> > wrote: > >> Yes, it needs to be aborted. >> Since API definition contains these mediation details, AFAIU this API >> would not even get published to the gateway without those. >> > Yeah, but Publishing an API is a different stage right? The imported API > will be in Created state. So I guess there won't be other issues when > importing the API. If the user gets any errors when he tries to publish the > API, he can attend to that and fix that manually. So since he has that > chance, I am in doubt whether we should hold the whole process rather than > giving a warning to the user and continue. > I am doubtful about that, Malintha. I agree with you about the point that an API will be imported and stay in 'Created' state. However that imported API can be a published API in its exported environment and user expects it to behave same here. That means a smooth transition from 'Created' to 'Published' just be changing the lifecycle. The only reason we avoided API importing in published state and limited to created state because there can be confusions/differences on the gateway environments of source (exported) and target(imported) environments. Please correct me if I have mistaken. As per my understanding, this tool is mostly useful to migrate published APIs among environments other than just created APIs. In that case, I wonder whether it's a good idea to allow API importing with mediation import errors as it would block the expected smooth transition. WDYT? Thanks. > >> Thanks. >> >> On Thu, Oct 20, 2016 at 10:24 AM, Nuwan Dias <[email protected]> wrote: >> >>> >>> >>> On Thu, Oct 20, 2016 at 9:37 AM, Kaveesha Perera <[email protected]> >>> wrote: >>> >>>> Hi all, >>>> >>>> Currently I'm working on a client side tool to perform import and >>>> export of APIs in APIM. >>>> >>>> On proceeding with importing a exported API, I came across a doubt >>>> state, Should we abort the normal process of API import if we failed to >>>> upload the corresponding mediation policies of that API, or should we allow >>>> the normal API import procedure even without mediation policies? >>>> WDYT? >>>> >>> >>> I think we should abort. Because if the API gets created with a >>> reference to the mediation policy, the API invocation will fail at the >>> runtime right? >>> >>>> >>>> Regards, >>>> Kaveesha. >>>> -- >>>> Kaveesha Perera >>>> Intern - Software Engineering >>>> >>>> mobile: 0716130471 >>>> >>> >>> >>> >>> -- >>> Nuwan Dias >>> >>> Software Architect - WSO2, Inc. http://wso2.com >>> email : [email protected] >>> Phone : +94 777 775 729 >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Best Regards, >> >> *Thilini Cooray* >> Software Engineer >> Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20774%20570112> >> E-mail : [email protected] >> >> WSO2 Inc. www.wso2.com >> lean.enterprise.middleware >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Malintha Amarasinghe > Software Engineer > *WSO2, Inc. - lean | enterprise | middleware* > http://wso2.com/ > > Mobile : +94 712383306 > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Best Regards, *Thilini Cooray* Software Engineer Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20774%20570112> E-mail : [email protected] WSO2 Inc. www.wso2.com lean.enterprise.middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
