Hi, If we are hard-coding default values to the bean class, are those values should be default to the component or to the product which is (frequently) using that component ? If we use default values related to the product then we can use that values directly in the specific product and if some other product is using that component, they have to override it in the deployment.yaml. For example product-is is using component identity-mgt. So what should be the default values for the config files coming from identity-mgt component ? Are those should be defaulted to the product-is related values or to the component related values and product-is should always override them from deployment.yaml.
Thanks! *Jayanga Kaushalya* Software Engineer Mobile: +94777860160 <+94%2077%20786%200160> WSO2 Inc. | http://wso2.com lean.enterprise.middleware On Wed, Nov 30, 2016 at 10:57 AM, Danesh Kuruppu <dan...@wso2.com> wrote: > Hi Dilan, > > If all user-configurable properties are not readily available in the .yaml >> file by default, how would a user know which >> properties are configurable and which are not ? >> > > All the configurable properties and their default values will be > documented. We are going to create this config document automatically by > reading the config bean class (using maven plugin). > We need to decide whether we pack those config documents in the product or > add to central location (doc page etc) > > Thanks > -- > > *Danesh Kuruppu* > Senior Software Engineer | WSO2 > > Email: dan...@wso2.com > Mobile: +94 (77) 1690552 <+94%2077%20169%200552> > Web: WSO2 Inc <https://wso2.com/signature> > > > _______________________________________________ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > >
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
