Cache resolve in sunbird content plugins.

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 - Bundle plugins with editor's artifact

We need to bundle plugins along with editor artefact, Let's say if Diksha (or) Sunbird instance needs some X Amount of plugins out of Y then only bundle and load X amount of plugin rather than making all plugins to globally available. This 

Plugins should follow the release deployment cycle similar to editor's. 

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:

1. Due to version maintains, Plugin cache will resolve.
2. Avoids the multiple portal deployment.

Cons:

1. Maintenance - As soon as version update, Admin as to update the sunbird player config through API.
2. Content Update

Conclusion: