Introduction:
This wiki explains the design and implementation of resolving sunbird-content-plugins cache.
Background:
Currently, If any fix/feature goes to contributed plugins other than the core plugins, The developers are publishing the plugins without any version bump-up and sunbird-portal deployment.
Problem Statement:
Currently, When the contributed/dynamic plugins are published the end user fails to get the latest changes of the published plugin due to cache.
Solution 1 - Plugin artifacts deployment
Let's say if Diksha needs some X Amount of plugins out of Y then only load X amount of plugin rather than making all plugins to globally available.
Should follow the release deployment cycle similar to content editor
Pros:
Cons:
- User will able to use only certain few plugins based on the configuration.
Solution 2 - Plugin version bump-up for the contributed plugins
Present:
Proposal:
As soon as the plugin fix is done before plugin get publish the developer must update the version of the plugin and sunbird-player config update update as well to avoid the cache.
Pros:
- Due to version maintains, Plugin cache will resolve.
- Avoids the multiple portal deployment.
Cons:
- Maintenance - As soon as version update, Admin as to update the sunbird player config through API.
- Content Update
Conclusion: