HTML plugin version is also available in flex serenity

[SreeSindhuSruth]

Hi,

When we register our HTML plugin, we are having the same plugin version in flex vsphere-client-serenity folder .Path is given below:

/etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity

We would like to know how to prevent this and let the plugin work only in HTML and the plugin shouldn;t appear in Flex.

[Denis_Chorbadzh · Accepted solution]

Hi,

In order for your plug-in to be deployed only on the HTML Client, the following dependency should be added to the plugin-package.xml : <pluginPackage id="com.vmware.vsphere.client.html" version="6.5.0" />

Your plugin-package.xml should contain both dependencies:

      <pluginPackage id="com.vmware.vsphere.client" version="6.5.0" />

      <pluginPackage id="com.vmware.vsphere.client.html" version="6.5.0" />

      <pluginPackage id="com.vmware.vsphere.client" version="6.5.0" />

      <pluginPackage id="com.vmware.vsphere.client.html" version="6.5.0" />

Best Regards,

Denis

[tganchev]

Denis's recommendation will ensure your plugin does not deploy on Flex.

The folder that you're seeing is just a cache that the Flex client is using to store downloaded plugins. A download is needed so that the client can inspect your plugin-package.xml to determine if the plugin needs to be deployed based on its required dependencies.

Delete your plugin's folder from vc-packages before trying out Denis's suggestion otherwise the cached version of the plugin from this folder will be used.

After restarting the vSphere client and logging into the UI you'd notice that the folder will be created again, but you will not have to care about it anymore.

[SreeSindhuSruth]

tganchev​ we have implemented what Denis suggested .deleted the plugin folder from vsphere-client-serenity.

after restarting we are seeing the plugin in sphere-client-serenity but not seeing the plugin in flex client.

Are you saying this is what is expected. Like we see the folder in serenity but not in UI?

Or do we have to delete the sphere-client-serenity folder itself and then restart the services?

[tganchev]

Yes, this is expected - the vsphere-client service downloaded the plugin, parsed the plugin-pakage.xml and determined that the plugin is not compatible with vsphere-client.

-Tony