> > Also, let's remove the unique index of CONFIG_ID in IDN_CONFIG_FILE table. > Then we can maintain multiple files for a given resource. >
+1. I will remove the unique index of CONFIG_ID in the IDN_CONFIG_FILE table. Thanks, Tharindu. On Tue, Dec 4, 2018 at 10:48 AM Isura Karunaratne <[email protected]> wrote: > Also, let's remove the unique index of CONFIG_ID in IDN_CONFIG_FILE table. > Then we can maintain multiple files for a given resource. > > Cheers, > Isura. > > On Tue, Dec 4, 2018 at 9:37 AM Tharindu Bandara <[email protected]> > wrote: > >> Hi Isura, >> >> We better to restrict this in API level since there is no need of having >>> config resources without config attributes or config file. >> >> >> +1. I will add this restriction in the API level. >> >> Thanks, >> Tharindu. >> >> On Tue, Dec 4, 2018 at 9:24 AM Isura Karunaratne <[email protected]> wrote: >> >>> Hi Tharindu, >>> >>> According to the database schema, we can add config resources without >>> any config attribute or config file. We better to restrict this in API >>> level since there is no need of having config resources without config >>> attributes or config file. >>> >>> Cheers, >>> Isura. >>> >>> On Mon, Dec 3, 2018 at 6:13 PM Tharindu Bandara <[email protected]> >>> wrote: >>> >>>> Hi all, >>>> >>>> Following is the diagramme for the $subject. Configuration store REST >>>> API for WSO2 IS[2] will be refactored to support this. >>>> >>>> >>>> Above diagramme is based on the following key points as discussed in >>>> the review meeting[1]. >>>> >>>> >>>> - >>>> >>>> Resources will be grouped under its type. Ex: For resources grouped >>>> under the issuer, type would be the issuer. >>>> - >>>> >>>> A resource can either contain a file or not. Ex: Email template >>>> file for the email resource. >>>> - >>>> >>>> A resource can contain zero or more attributes. Ex: For an email >>>> resource, from and to values are attributes. >>>> - >>>> >>>> Attributes and the file will be kept in separate tables and boolean >>>> flags will be included in the resource table to indicate the existence >>>> of >>>> each category. >>>> >>>> [1] "Invitation: [IAM][Review]JDBC Based Configuration Store @ Mon Dec >>>> 3, 2018 1pm - 2pm (IST) (WSO2 Engineering Group)" >>>> >>>> [2] "[Architecture] [IS] JDBC based Configuration Store for WSO2 IS" >>>> >>>> Thanks, >>>> >>>> Tharindu. >>>> -- >>>> *Tharindu Bandara* >>>> Software Engineer | WSO2 >>>> >>>> Email : [email protected] >>>> Mobile : +94 714221776 >>>> web : http://wso2.com >>>> <https://www.google.com/url?q=http://wso2.com&sa=D&ust=1517653383990000&usg=AFQjCNFggB4bSJTKmdqKcBV0VY9xx1ABKg> >>>> >>>> https://wso2.com/signature >>>> >>> >>> >>> -- >>> >>> *Isura Dilhara Karunaratne* >>> Associate Technical Lead | WSO2 <http://wso2.com/> >>> *lean.enterprise.middleware* >>> Email: [email protected] >>> Mob : +94 772 254 810 >>> Blog : http://isurad.blogspot.com/ >>> >>> >>> >>> >> >> -- >> *Tharindu Bandara* >> Software Engineer | WSO2 >> >> Email : [email protected] >> Mobile : +94 714221776 >> web : http://wso2.com >> <https://www.google.com/url?q=http://wso2.com&sa=D&ust=1517653383990000&usg=AFQjCNFggB4bSJTKmdqKcBV0VY9xx1ABKg> >> >> https://wso2.com/signature >> > > > -- > > *Isura Dilhara Karunaratne* > Associate Technical Lead | WSO2 <http://wso2.com/> > *lean.enterprise.middleware* > Email: [email protected] > Mob : +94 772 254 810 > Blog : http://isurad.blogspot.com/ > > > > -- *Tharindu Bandara* Software Engineer | WSO2 Email : [email protected] Mobile : +94 714221776 web : http://wso2.com <https://www.google.com/url?q=http://wso2.com&sa=D&ust=1517653383990000&usg=AFQjCNFggB4bSJTKmdqKcBV0VY9xx1ABKg> https://wso2.com/signature
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
