Hi, Currently we are providing patches to PPaaS cartridge agent as artifacts to be replaced manually. This is because cartridge agent does not have an OSGi run time. But this goes against the support model that we are following in other components. It will be very hard to keep track of patches applied if we continue like this.
This can be improved by creating Puppet scripts to simulate the support patching process. Patches for cartridge agent should be placed inside <agent puppet module>/files/patches/ directory. Puppet should go through all the patches available and apply them accordingly (simulate Carbon patching process). The patches may include jar artifacts, extension scripts, configuration scripts and server startup scripts. My suggestion is to automate patching all these artifacts via Puppet rather than having to manually replace them. This includes patching scripts as well, not just jars artifacts. If we define a proper directory structure for patches, this can be easily achieved. In that way we can easily keep track of changes and rollback quickly if needed. Any thoughts? -- Akila Ravihansa Perera Software Engineer WSO2 Inc. http://wso2.com Phone: +94 77 64 154 38 Blog: http://ravihansa3000.blogspot.com _______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
