Plug-In Caching

When the vSphere Client installs a plug-in, it downloads the plug-in manifest file and caches it. The cached copy is re-used whenever the vsphere-ui process restarts.

After a plug-in has been unregistered, the vsphere-ui service detects the change immediately. The cached copy of the plug-in manifest is deleted from the cache.

When a plug-in is upgraded, the vsphere-ui service detects the change as soon as the plug-in registration entry is updated with a new version number. At that time, the old plug-in version is undeployed, the cached copy of the manifest is removed, and the new plug-in version is deployed.

If plug-in resources are upgraded without changing the version number, such as when developing a plug-in, the vsphere-ui service does not detect the change. To deploy plug-in changes during development, use pluginDeveloperMode to enable the Redeploy button in the user interface. For more information, see #GUID-CD886621-4D1F-426E-A78D-67A54CE726CC.