VMware Employee
VMware Employee

vSphere Client SDK 6.7U2 is out !!!

Hi all,

vSphere 6.7U2 is now GA and so are the SDKs. Release notes will be up soon but here are some highlights.

 

This release of the vSphere Client contains 2 signficant changes related to plugins:

  1.  Improvement on troubleshooting and monitoring of plugins through the vSphere Client: Plugin Management UI. To get an overview follow the vSphere Blog and watch this video: https://www.youtube.com/watch?v=ztvxeDxG0NY .

  2.  Virgo server has been replaced by its building blocks: Tomcat + Equinox + Spring. The change has no impact on existing plugins and is done to make sure library security fixes are consumed without the need to bump other libraries (which was the cause of the major Spring upgrade in 6.7GA). Please let us know in case of any issues.

 

Some SDK details:

  1.  Both home pages of vSphere Client SDK and vSphere Web Client SDK have been enhanced to ease decision making of what plugin type to build based on your current requirements and future plans. Have a look also at the linked resources column which now contains the UX guidelines for HTML plugins.

  2.  Improvements for faster Remote plugin development: 

       - The flag remote.plugin.updateOnBrowserRefresh=true added to webclient.properties file allows quick redeployment of a remote plugin during development.

       - The plugin manifest converter helps translating your old local plugin XML manifest to a remote plugin JSON manifest. Note the feature sets differ so this is not always 1:1 mapping but guidance on various scenarios is provided.

  3.  Fixes to plugin modal sizing and remote plugin localization.

 

As always, please give it a try and let us know of any feedback.

 

Cheers,

Vladi

0 Kudos
2 Replies
Contributor
Contributor

Is there a beta vSphere client SDK for 7.0 ?

0 Kudos
VMware Employee
VMware Employee

Hi Abby,

With regards to releases no particular numbering after 6.7U2 has been decided or announced.

Regardless of whether you refer to a major or a minor future version of the SDK we don't currently plan any backward compatibility changes (e.g. removal of APIs) that absolutely require a beta SDK. If such a need arises we will make sure to give a heads up in the forum and other channels.

Backward compatibility aside, we might provide an early access SDK in case there are major improvements / new APIs to try out but the scope is not clear yet.

Cheers,

Vladi

0 Kudos