Hi Chamin/Sachini, AFAIU we are going to use labels when downloading a subset of APIs via Microgateway. If it is not mandatory to have the labels, how are we going to handle the APIs without labels in Microgateway? Are we not going to download the APIs without labels?
Thanks, Naduni On Thu, May 3, 2018 at 8:39 PM, Sachini De Silva <[email protected]> wrote: > Hi Thilini, > > As per the discussions so far, it is not mandatory to attach a label to an > API. So I guess there won't be a concept as default label for APIs. > > An API can have zero or more labels attached to it. More details related > to this can be found in [1]. > > [1]. [Architecture][APIM] Label feature for API-Manager gateway > > Thanks, > Sachini > > On Thu, May 3, 2018 at 8:31 PM, Thilini Shanika <[email protected]> wrote: > >> Hi Chamin, >> >> Need some clarification regarding the feature. >> >> Is it mandatory to attach a label to an API? Or are we planning to have a >> dedicated label which will be assigned to APIs as the default label? >> >> On Thu, May 3, 2018 at 3:31 PM, Chamin Dias <[email protected]> wrote: >> >>> Hi all, >>> >>> This is regarding the design of $subject. >>> >>> *Initial flow* >>> >>> 1. Labels are added through the admin dashboard UI / admin REST API >>> (Reference : Mail thread - *[Architecture][APIM] Label feature for >>> API-Manager gateway >>> <http://mail.wso2.org/mailarchive/architecture/2018-May/030687.html>*) >>> >>> 2. When creating an API using publisher UI, we will display existing >>> labels using a multi select drop down (labels are fetched from getAllLabels >>> REST API). When it comes to REST API payload (for API creation), we can >>> introduce new section/array for this. >>> >>> 3. Upon saving/publishing the API, we have identified 3 options to save >>> the label(s) of that API. >>> a) Save as a registry property >>> b) Save in the RXT >>> c) Save in the DB - keep a mapping in the API table >>> >>> Note : Saving in the RXT is the best option becasuse it will faclilitate >>> for searching and migration. >>> >>> >>> *Impact on API import/export* >>> >>> The $subject has an impact on API import/export as well. >>> >>> Fact 1 : When exporting the API, we need to make sure that the labels >>> are preserved (i.e - the exported zip archive should contain the label(s)). >>> Fact 2 : When importing the API, we can create the labels (if there are >>> new, compared to the existing labels in the system) and attach. If the >>> labels are already there, we can just attach them to the newly created API. >>> >>> This is the initial design for $subject. Please share your thoughts on >>> this. It is highly appriciated. >>> >>> Thanks. >>> >>> -- >>> Chamin Dias >>> Mobile : 0716097455 >>> Email : [email protected] >>> LinkedIn : https://www.linkedin.com/in/chamindias >>> >>> >> >> >> -- >> Thilini Shanika >> Senior Software Engineer >> WSO2, Inc.; http://wso2.com >> 20, Palmgrove Avenue, Colombo 3 >> >> E-mail: [email protected] >> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > > *Sachini De Silva* > Software Engineer - WSO2 > > Email : [email protected] > Mobile : +94714765495 > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Naduni Pamudika* Software Engineer | WSO2 Mobile: +94 719 143658 <+94%2071%20914%203658> [image: http://wso2.com/signature] <http://wso2.com/signature>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
