Best Practices to adhere when using WSO2 Updates¶
Here are the guidelines and recommendations to receive best update experience with WSO2 Updates 2.0.
Frequent update of products will ensure the product is bug free and always up to dated with new features, security enhancements and improvements. WSO2 recommends updating your systems weekly or bi-weekly. Before directly applying any updates to your production system, WSO2 always recommends applying any update to lower environments such as testing, development or staging environments which has a similar product distribution as in production environment.
Before you run the update tool, remember to stop the product pack from running.
2. Add custom configurations or modifications
Follow guidelines when adding customization to product pack files. This will reduce the merge conflicts. Refer how to reduce merge conflicts.
3. Run tests
WSO2 thoroughly tests and certifies each update and hotfix released. Regardless of whether an update or hotfix running tests on your update environment ensures that all existing and new functionalities are working perfectly fine.
Whenever you apply an update WSO2 recommends you to apply the updates to lower environments, run tests and update the production environment.
4. Getting Updates to a lockdown Environment
The best practices disseminating updates to production environment with no internet connection is as follows:
First receive the updates in a lower environment that is connected to the internet. Test the environment thoroughly. Perform security checks mandate by your organization and verify the updated pack. Last move the verified pack to the lockdown environment securely.
5. Use a Configuration Management tool.
There are a myriad of benefits of using a Configuration Management Tool. WSO2 advise the use of Configuration Management Tool such as Puppet and Ansible to carry configuration changes flawlessly. Read more on our Continuous Update Document.