I would like to propose to use a single YAML file for each distribution (product/profile) to make the configuration process easier.
I understand that we are trying to do something similar using a properties file (by overriding configurations in separate files), however IMO a properties file might not suite well for this purpose. A YAML file or any other type of a file which is more readable and designed for managing hierarchical data structures would work well. More importantly having a single configuration file would make the configuration process more simpler and clean. WDYT? Thanks On Thursday, October 13, 2016, Sidath Weerasinghe <sid...@wso2.com> wrote: > Hi Jayanga, > > What are the most frequently changing configurations in C5 which are going > to store in the deployment.properties" file ? > > On Thu, Oct 13, 2016 at 5:07 PM, Jayanga Dissanayake <jaya...@wso2.com > <javascript:_e(%7B%7D,'cvml','jaya...@wso2.com');>> wrote: > >> Hi All, >> >> With C5, we introduced "ConfigResolver" which enhances the user >> experience in changing configuration values. With the previous C4x >> approach, users had to know where the configuration files are and to, >> change several configuration files to get the product working in some >> scenarios. >> >> With "ConfigResolver" it allows us to have more frequently changing >> configurations in one location "deployment.properties" file. >> >> A product has set of configurations that are needed to be changed in the >> deployments and there are some other configurations that we don't change >> unless there is a complex situation. Hence, ideally, deployment.properties >> file should contain only the configurations that are frequently used and >> can add more entries if a requirement arise. >> >> But with the requirements coming in with the "profile" support [1]. we >> have to rethink the way config resolver handle the configuration files. >> >> eg: >> 1. We need to enable indexing in API store and publisher, not in other >> profiles. >> 2. Enabling certain handlers in particular profiles. >> >> At present, there is no configuration to enable/disable these features. >> We have to rethink the way we define configurations in features in future. >> We have to have a way to enable/disable certain features so that those >> could be disabled in certain profiles. >> >> Any idea/questions/clarifications are highly appreciated as it will help >> to model the new configurations story in C5. >> >> [1] "Multiple profile support for C5 based products." >> >> Thanks, >> *Jayanga Dissanayake* >> Associate Technical Lead >> WSO2 Inc. - http://wso2.com/ >> lean . enterprise . middleware >> email: jaya...@wso2.com >> <javascript:_e(%7B%7D,'cvml','jaya...@wso2.com');> >> mobile: +94772207259 >> <http://wso2.com/signature> >> >> _______________________________________________ >> Architecture mailing list >> Architecture@wso2.org >> <javascript:_e(%7B%7D,'cvml','Architecture@wso2.org');> >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Thank You, > Best Regards, > > Sidath Weerasinghe > > > *Intern* > > *WSO2, Inc. * > > *lean . enterprise . middleware * > > > *Mobile: +94719802550* > > *Email: *sid...@wso2.com <javascript:_e(%7B%7D,'cvml','sid...@wso2.com');> > > Blog: https://medium.com/@sidath > > Linkedin: https://lk.linkedin.com/in/sidathweerasinghe > -- *Imesh Gunaratne* Software Architect WSO2 Inc: http://wso2.com T: +94 11 214 5345 M: +94 77 374 2057 W: https://medium.com/@imesh TW: @imesh lean. enterprise. middleware
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
