Hi, It would be a good feature to allow a --test flag in wso2server.sh which doesn't start the server but accomplishes the following tasks.
1. Validate all configuration files with respect to component functionality 2. Validate if dependency libs are present 3. Provide a valid return code for success (0) or failure (more than 0) 4. Does not cause any side effects (DB creation/modification, log generation etc) The use case for this would be when sys admins or developers configure (mostly not for the first time) servers to be directly deployed that would have some effect on the department level (not directly to production, but, say, for dogfood servers). Certain configuration options cannot be validated until the server has started/run for a while and caused side effects like database creation that cannot be easily rolled back. A dry run would enable them to test the configuration changes without actually causing those side effects. Configuration Automation solutions like Puppet or Chef could solve this issue on their layer, however not all levels of users have configuration automation deployed at initial stages. Every component that gets affected by any part of the configuration can implement a validation step that gets invoked upon --test flag to starter script. WDYT? Regards, Chamila de Alwis Committer and PMC Member - Apache Stratos Software Engineer | WSO2 | +94772207163 Blog: code.chamiladealwis.com
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
