topic vSphere Client SDK 7.0 Update 1 is GA! in vSphere Client SDK Discussions

vSphere Client SDK 7.0 Update 1 is GA!

_vladi_ — Tue, 06 Oct 2020 22:09:02 GMT

Hi plugin developers,

vSphere 7.0U1 is out. The new vSphere Client SDK contains cool new stuff for plugins, most notably:

- Dynamic remote plugin extensions (ability to show/hide plugin items).

- Plugin multi-manifest support (enables taking advantage of new APIs while preserving compatibility with older vSphere Client releases).

- Actions on multiple targets (e.g. on a selection of multiple VMs).

Meanwhile the vSphere Client has made a huge step forward with accessibility & icons. We recommend plugins to follow suit and make plugin views more accessible.

If you have any suggestions or ideas on how to improve the vSphere Client or the plugin support you can now use the vSphere Ideas section of the Client's Feedback menu (top-right).

SDK bits & docs: SDK home page, Release Notes

Cheers,

Vladi

Re: vSphere Client SDK 7.0 Update 1 is GA!

kumar_t — Mon, 02 Nov 2020 12:13:14 GMT

Hi vladi,

I'm trying to register and run the remote plugin sample in vCenter Client 7.0(vSphere Client version 7.0.0.10100).

Plugin is not deployed and giving the below error:

Plugin json manifest validation failed. Check the detailed information of the relevant vCenter Server task in the Task Console. com.vmware.vise.extensionfw.impl.plugin.util.PluginManifestValidationException: Plugin manifest failed schema validation: file:/etc/vmware/vsphere-ui/vc-packages/vsphere-client-serenity/com.vmware.sample.remote-1.0.0.0/plugin.json Errors: $.requirements.plugin.api.version: does not have a value in the enumeration [1.0.0, 1.0.1, 1.1.0] $.requirements.plugin.dynamic.extensions: is not defined in the schema and the schema does not allow additional properties $.manifestVersion: does not have a value in the enumeration [1.0.0, 1.0.1, 1.1.0] $.objects.VirtualMachine.configure.views[0].dynamic: is not defined in the schema and the schema does not allow additional properties $.objects.VirtualMachine.configure.dynamicUri: is not defined in the schema and the schema does not allow additional properties $.objects.VirtualMachine.menu.dynamicUri: is not defined in the schema and the schema does not allow additional properties $.objects.VirtualMachine.menu.actions[0].id: is not defined in the schema and the schema does not allow additional properties $.objects.VirtualMachine.menu.actions[0].dynamic: is not defined in the schema and the schema does not allow additional properties com.vmware.vise.extensionfw.impl.plugin.JsonPluginManifestParserImpl.parse(JsonPluginManifestParserImpl.java:59)

Can't we run vSphere 7.0U1 sample in vSphere 7.0 GA client?

Thanks,

Kumar

Re: vSphere Client SDK 7.0 Update 1 is GA!

_vladi_ — Mon, 02 Nov 2020 12:46:27 GMT

Hi Kumar,

No, SDK samples are normally not compatible with the previous vSphere Client release as we are updating them to demonstrate new features that don't exist in previous version.

So 7.0U1 sample works on vSphere 7.0U1+ client.

That said, you can use the multi-manifest feature to build a remote plugin with 7.0U1 SDK that is validated correctly on previous releases.

Cheers,

Vladi

Re: vSphere Client SDK 7.0 Update 1 is GA!

kumar_t — Tue, 10 Nov 2020 14:04:42 GMT

Im trying to use SHA 256 of vCenter 7.0U1 for vCenter registration and manifest server run

java -jar target\remote-plugin-sample-7.0.1.00000-SNAPSHOT.jar --vcenter.guid=a7020581-6ae0-4973-a1a8-72956b7e69f5 --vcenter.thumbprint=3e5e1dba4cd04f550f9f6311ff0a5a45ae58a4ca0f7b0bf1727c967c26ada6a5 --vcenter.fqdn=VC_FQDN --vcenter.port=443

.\extension-registration.bat -action registerPlugin -remote -url https://VC_FQDN/sdk -username administrator@vsphere.local -password password1! -key com.vmware.sample.remote -version 1.0.0 -pluginUrl https://<MANIFEST_SERVER>:8443/sample-ui/plugin.json -serverThumbprint 59:93:D9:CF:54:CB:32:60:93:58:CE:45:AD:4D:D7:1F:1C:08:1D:0D:B6:A5:3D:F5:3E:D7:A9:CA:E2:32:DE:41 -c 'Example, Inc.' -n 'RemoteU1 Plug-in' -s 'This is a sample plug-in' --taskList C:\Users\Administrator\Desktop\registration\resources\taskList.json --faultList C:\Users\Administrator\Desktop\registration\resources\faultList.json --privilegeList C:\Users\Administrator\Desktop\registration\resources\privilegeList.json --resourceList C:\Users\Administrator\Desktop\registration\resources\resourceList.json -vct 3e5e1dba4cd04f550f9f6311ff0a5a45ae58a4ca0f7b0bf1727c967c26ada6a5 <-- VC's SHA 256 fingerprint

we are seeing the attached deployment error. But if we use SHA1 fingerprint it is getting deployed. Is this expected behavior?