On Wed, May 2, 2018 at 6:26 PM, Krishan Wijesena <[email protected]> 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. > > > > *Multi-Tenant support* > > We need to support the multi-tenancy of the adding labels. > > Super/Tenant admin can define new labels based on the requirement. > > So I introduce the TENANT_ID field to the AM_LABEL table. > > For example, Tenant_admin_A and Tenant_admin_B can introduce the same > label "X" which have two base_path. > > Comments or suggestions are highly appreciated. > > Thanks & Regards > -- > > *Krishan Wijesena* > Software Engineer | WSO2 > > Email : [email protected] > Mobile : +94776219923 > WSO2 Inc : http://wso2.com > [image: http://wso2.com/signature] <http://wso2.com/signature> > -- Harsha Kumara Software Engineer, WSO2 Inc. Mobile: +94775505618 Blog:harshcreationz.blogspot.com
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
