Denis_Chorbadzh's Posts

Hi Folks, The new vSphere 8.0 release brings significant improvements to the Plug-in Administration view, Integrated Solution Installer for the vSphere Client, new capabilities, enhanced features an... See more...
Hi Folks, The new vSphere 8.0 release brings significant improvements to the Plug-in Administration view, Integrated Solution Installer for the vSphere Client, new capabilities, enhanced features and bug fixes. Note: Local plug-ins are deprecated and, although still functional, VMware plans to discontinue their support with the next major release. What's new for vSphere Client extensibility and remote plug-ins: vSphere Client Plug-ins Administration View Overhaul - the page offers a much more sophisticated view of the plug-ins and their topology, making it easy to verify which vCenter Server a particular plug-in is registered with, and which plug-in servers are in use Integrated Solution Installer for the vSphere Client - partners now have the ability to integrate their solutions with the Solution Installer in the vSphere Client Navigating Actions Defined in the Remote plug-in Manifest File - developers are now able to define navigating actions along with the modal menu actions in the plug-in manifest file. This will enable users to use the action to navigate to a view defined by the plug-in Newly Promoted Core Client Views for Remote plug-in Navigation - the list of views to which a remote plug-in can navigate with the navigateToClientView() JavaScript API has been extended Sharing Modal Dialogs Between Remote plug-ins - remote plug-ins can create more distributed content sharing. Modals defined by one remote plug-in can be reused by a different remote plug-in Refreshing Remote plug-in Related Items - remote plug-ins can refresh their related items by using the new JavaScript API – refreshPluginItemsState() Support for Italian Localization - the vSphere Client SDK now allows localization of plug-ins in the Italian language Support Dynamic Object Cards - in addition to dynamic monitor, configure and action extensions, remote plug-in developers are able to define dynamic cards Support for Additional Plug-in Servers for Dynamic Extensions - developers can now specify a server endpoint for dynamic extension queries. Formerly, the manifest server was required to handle all dynamic extension queries Remote Plug-in Sample updates New library versions: Clarity Design System 3.0.0 and Angular 9.0.0. The sample demonstrates the use of dynamic cards   Resolved issues: Open a modal with a recursive object - The htmlClientSdk.modal.open() method throws an error when a configuration object with recursive references is passed. A new flag sanitizeData was introduced indicating whether the passed modal configuration data should be serialized/deserialized, or not. The default value of the flag is true (i.e., do serialization), which is the previous behavior. Set the flag to false if you pass objects containing recursive references Modified the Remote Plug-in Sample to use a more secure trust strategy - previous versions of the sample used a "trust-all" strategy, which was insecure. This version correctly verifies server thumbprints Plug-in manifest conversion tool is modified to support both light and dark themes - the tool is modified to generate two sprite sheets, one for the light theme and one for the dark theme. The sprite sheets now contain placeholder icons which should be replaced by the plug-in developers with real icons Fixed a number of layout issues with the plug-in modal dialogs - fixed the layout of the modal dialogs opened through the vSphere Client SDK JavaScript APIs to eliminate issues previously reported   For more information, check the official SDK documentation page, the release notes and this blog post. As always, feel free to share your feedback and ideas with us.   Best Regards, Denis    
Hi Kumar,   This JS API refreshes the plugin views that rely on filtering conditions. For example: Plugin A introduces a view that is dynamically filtered based on a property value of some object.... See more...
Hi Kumar,   This JS API refreshes the plugin views that rely on filtering conditions. For example: Plugin A introduces a view that is dynamically filtered based on a property value of some object. If the property value is changed by the plug-in using the public vSphere APIs, then the plug-in needs to call this API to signal the UI to re-evaluate the state of the initiator's plug-in related items. Usage: htmlClientSdk.app.refreshPluginItemsState(); Let us know if you have any questions. Best Regards, Denis
Hi,   Unfortunately, we are not able to provide a direct help since this forum is concerned with vSphere Client plugin development and APIs. If you want to access some vCenter Server APIs, you can... See more...
Hi,   Unfortunately, we are not able to provide a direct help since this forum is concerned with vSphere Client plugin development and APIs. If you want to access some vCenter Server APIs, you can contact the folks from the Management SDK.   Best Regards, Denis
Hi,   Thank you for contacting us. As this forum is mainly concerned with vSphere Client SDK and Plugins, we are not able to provide a concrete answer. I suggest looking into the Automation SDK f... See more...
Hi,   Thank you for contacting us. As this forum is mainly concerned with vSphere Client SDK and Plugins, we are not able to provide a concrete answer. I suggest looking into the Automation SDK for Java page: https://developer.vmware.com/web/sdk/7.0/vsphere-automation-java.   Best Regards, Denis
Hi @sujeetmkalaskar ,   Yes, all extension points described in the 7.0 Update 3 documentation will work in vSphere Client 8.0.   Best Regards, Denis
Hi,   The plugin manifest converter tool works well in the general use case, however, it may not work correctly when encountering some plugin specifics. Plugin developers may have really complex pl... See more...
Hi,   The plugin manifest converter tool works well in the general use case, however, it may not work correctly when encountering some plugin specifics. Plugin developers may have really complex plugin structure, or they may have chosen different file structure, file names, file contents etc. Even though the tool may be helpful, we recommend developers to write their plugin.json manually after carefully reading the documentation. This will improve their understanding of the plugin.json semantics and usage, and will prevent many problems.   Best Regards, Denis  
Hi,   You can find all the available extension points in the official documentation: https://developer.vmware.com/web/sdk/7.0/client Look into: Developing Remote Plug-ins with the vSphere Client S... See more...
Hi,   You can find all the available extension points in the official documentation: https://developer.vmware.com/web/sdk/7.0/client Look into: Developing Remote Plug-ins with the vSphere Client SDK (7.0 Update 3) And: Remote Plug-in Manifest Schema   Best Regards, Denis
Hi,    I have tried to register the vSphere Client SDK sample plugin using the following command: ./extension-registration.sh -action registerPlugin -k com.vmware.sample.remote -v 1.0.0 -url https... See more...
Hi,    I have tried to register the vSphere Client SDK sample plugin using the following command: ./extension-registration.sh -action registerPlugin -k com.vmware.sample.remote -v 1.0.0 -url https://<my_vcenter>/sdk -username administrator@vsphere.local -password 'myPassword' -st 55:5D:B1:0D:E0:33:3E:10:AB:1E:F4:86:62:61:F0:7F:93:FE:F6:9B -pu https://<plugin_server>:8443/sample-ui/plugin.json -remote --taskList=../../../samples/remote-plugin-sample/registration/resources/taskList.json --faultList=../../../samples/remote-plugin-sample/registration/resources/faultList.json --privilegeList=../../../samples/remote-plugin-sample/registration/resources/privilegeList.json --resourceList=../../../samples/remote-plugin-sample/registration/resources/resourceList.json   At first the plugin tasks we not localized but after a logout and login, the tasks were localized correctly. One difference that I am seeing is that you are not using '=', for example, --resourceList=../../../samples/remote-plugin-sample/registration/resources/resourceList.json   Let us know if you succeed.   Best Regards, Denis
Hi,   Make sure you have the latest version of the SDK downloaded. The option may not be present for older SDK versions.   Best Regards, Denis
Hi,   Unfortunately, we are not able to provide an insight on this issue as this forum is concerned with vSphere Client SDK and Plugins. Try posting your question in the general forum or a specifi... See more...
Hi,   Unfortunately, we are not able to provide an insight on this issue as this forum is concerned with vSphere Client SDK and Plugins. Try posting your question in the general forum or a specific forum of the used SDK.   Best Regards, Denis
Hi,   You can refer to one of the following suggestions: https://communities.vmware.com/t5/VMware-vCenter-Discussions/Change-VCenter-6-5-HTTPS-port/td-p/492532 https://williamlam.com/2016/01/how-... See more...
Hi,   You can refer to one of the following suggestions: https://communities.vmware.com/t5/VMware-vCenter-Discussions/Change-VCenter-6-5-HTTPS-port/td-p/492532 https://williamlam.com/2016/01/how-to-change-the-default-ports-on-the-vcenter-server-appliance-in-vsphere-6-0.html   Best Regards, Denis
Hi,   Currently, it is not possible to call vCenter Server's REST APIs directly from the plugin's backend by using the cloned session.   Best Regards, Denis
Hi,   Currently, it is not possible to call vCenter Server's REST APIs directly from the plugin's backend by using the cloned session.   Best Regards, Denis
Hi,   Unfortunately, we are not able to provide a direct help since this forum is concerned with vSphere Client plugin development and APIs. You can post your request in the general vCenter Server... See more...
Hi,   Unfortunately, we are not able to provide a direct help since this forum is concerned with vSphere Client plugin development and APIs. You can post your request in the general vCenter Server forum. In addition, if you want to access some vCenter Server APIs from your plugin, you can contact the folks from the Management SDK.   Best Regards, Denis
Hi,   Yes, once you have acquired the cloned user session, you can use the vimPort to call different vCenter Server APIs. We have an example of how to check for certain user privileges in our remo... See more...
Hi,   Yes, once you have acquired the cloned user session, you can use the vimPort to call different vCenter Server APIs. We have an example of how to check for certain user privileges in our remote plugin sample present in the vSphere Client SDK deliverable. The code that shows this is in: <sdk-folder>/samples/remote-plugin-sample/src/main/java/com/vmware/sample/remote/vim25/services/AuthorizationService.java   Best Regards, Denis
Hi,   You can use any technology of choice for your plugin's front-end. The front-end API for remote plugins is written in pure JavaScript so you can use it in any technology.   Best Regards, D... See more...
Hi,   You can use any technology of choice for your plugin's front-end. The front-end API for remote plugins is written in pure JavaScript so you can use it in any technology.   Best Regards, Denis
Hi folks, The new vSphere Client SDK 7.0 Update 2 is out! The new release comes with some quality improvements: The vSphere Client 7.0 Update 2 is compliant with the Federal Information Processin... See more...
Hi folks, The new vSphere Client SDK 7.0 Update 2 is out! The new release comes with some quality improvements: The vSphere Client 7.0 Update 2 is compliant with the Federal Information Processing Standards (FIPS). There are also local plugin recommendations for FIPS compliance. Plugin download retry mechanism - to save you from cases when the plugin download URI might be temporarily unavailable. For a more detailed look, please go the the SDK Home Page and see the full list of Release Notes. Best Regards, Denis  
Hi,   Unfortunately, we could not advise you on that issue. This forum is mainly concerned with vSphere Client extensibility and plug-ins. You may try posting your question to some of the other fo... See more...
Hi,   Unfortunately, we could not advise you on that issue. This forum is mainly concerned with vSphere Client extensibility and plug-ins. You may try posting your question to some of the other forums.   Best Regards, Denis
Hi, For exploring the vCenter Server rest APIs, you can go to the vSphere Client -> Home -> Developer Center -> API Explorer. There you may find all information about the different APIs.   Best Re... See more...
Hi, For exploring the vCenter Server rest APIs, you can go to the vSphere Client -> Home -> Developer Center -> API Explorer. There you may find all information about the different APIs.   Best Regards, Denis
Hi Michael,   Yes, you can check the logged in user's privileges -  we have demonstrated how to do this in our remote plugin sample: /samples/remote-plugin-sample/src/main/java/com/vmware/sample/r... See more...
Hi Michael,   Yes, you can check the logged in user's privileges -  we have demonstrated how to do this in our remote plugin sample: /samples/remote-plugin-sample/src/main/java/com/vmware/sample/remote/vim25/services/AuthorizationService.java In 7.0 U1 we have introduced the notion of Dynamic Extensions which enable you to show/hide (enable/disable) certain UI extensions based on a condition. We have also demonstrated this in our latest changes to the remote plugin sample: /samples/remote-plugin-sample/src/main/java/com/vmware/sample/remote/controllers/DynamicItemsController.java You can read more in the official documentation. Have in mind that this is not supported in 6.7 U3. For previous versions, you can just show an information to the user that the view is not available.   Let us know if you have any questions.   Best Regards, Denis