Hi Krishan On Thu, May 3, 2018 at 12:53 PM Harsha Kumara <hars...@wso2.com> wrote:
> > > On Wed, May 2, 2018 at 6:26 PM, Krishan Wijesena <krish...@wso2.com> > wrote: > >> Hi All, >> >> >> Currently, I'm working on the Labeling feature for API Manager gateway. >> API Manager need to allows adding labels to the APIs in create/update >> phases from the publisher, so that labels help to grouping APIs into API >> manager gateway. >> >> If the user requests the particular label, then it provides the set of >> APIs that deploy in the same gateway. >> >> As initial phase, labels should be defined by the admin(Super/Tenant) >> using admin dashboard and the particular label should have set of >> properties. >> >> To do that I need to introduce AM_LABEL table to the AM database to store >> the labels and it’s schema as follows. >> >> LABEL_ID is the primary key and (NAME & TENANT_ID) is Unique. >> >> Label should have separate Http and Https basepath. >> > What will be store in base path? Basically we can create labels and > assigned them to APIs. > >> >> >> >> We only need label_id and it can be a UUID value. HTTP/HTTPS base paths are wrong. This has to be the access urls of the gateway. For an exmaple we can have the label called Public and it can have the following access urls. http://wso2.gw.com https://wso2.gw.com Additionally we need to add WebSocket endpoints as well. So we need to have 4 types of access urls in here. Are we not using the endpionts defined in APIGateway section here after or what is the strategy going forwar? Are we adding a default label for APIs when creating/publishing? Thank you! -- *Pubudu Gunatilaka* Committer and PMC Member - Apache Stratos Senior Software Engineer WSO2, Inc.: http://wso2.com mobile : +94774078049
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
