Skip to main content

Code Capture - Developer Center

From vSphere 6.7 onwards VMware introduced a section called the Developer Center where it provides a location for you to browse through the API structure and understand how to call and use the API. There is a section called "Code Capture" where once you set it up you can record your steps that you perform in GUI and then it will translate those steps to code.

In vSphere 6.7 you could only get PowerCLI but with vSphere 7.0 you can have PowerCLI, vRO Javascript, Python, and Go. The following steps are not available for recording - roles, privileges, tags, content libraries, storage policies and passwords at present.

How to get started?
  • In vSphere click on Menu and select Developer Center
  • Select Code Capture tab and if you have not enabled code capture before then you should see the screen below. Click on the slider to enable code capture
  • Once you have enabled code capture you should see the start record button and also on the top right you should see a record icon button. At this point you can either press start record button or navigate to where you want to record and then press the record icon button. The record icon should flash and change as you are recording.
  • Once you have finished press the record icon on the top right and it should bring you back to the code capture screen where you can see the code in PowerCLI for creating a datacenter. To view the code in a different language click on PowerCLI
  • Now you can see that the code is in Javascript
  • You can now copy or download the code to be used. As you have now enabled code capture you can capture the code anytime by pressing the record icon on the top right of the screen. You will get the prompt below when you first do it and you can select the option to not show the warning again
This is a great little tool to help you capture what commands are needed to achieve some of the tasks that you would like to use code to perform for you. It may not be the perfect code but for me at least I can see what cmdlet was used to perform some of the task to give me an idea.
Just to reiterated the following steps are not available for recording - roles, privileges, tags, content libraries and storage policies at present and passwords are not recorded either.

Comments

Popular posts from this blog

Rolling back a version of ESXi

There is an option in VMware where after you have performed an major upgrade of ESXi you can roll back to your previous version. The benefit of this is that you would not need to reinstall your ESXi and its configuration if you had issues with the new software. I had to do this on one occassion in my lab where I upgraded from 6.5 to 6.7 and my VMs would not run because the CPU was not supported in 6.7. Please remember if you are using ISO method to upgrade ESXi please ensure you select "Upgrade ESXi, preserve VMFS datastore". Selecting "Install ESXi, preserve VMFS datastore" does not mean preserving datastore means retaining ESXi as it will still do a clean install of ESXi. This method does not work for vSphere 7.0 as there are changes to the partitions on the boot device. Below are the steps to roll back to a previous version which is quite straight forward. As always perform an backup of your host configuration before you upgrade or rollback ( KB2042141 ). I have

Configuring ESXi 6 host to send logs to Syslog Server

In my previous post I talked about configuring VMware Syslog server for Windows which is installed and enabled by default on installation of vCenter 6 for Windows. I will now describe the basic configuration that is required on an ESXi 6 host to be able to send logs out to a syslog server using my vCenter as the example. 1) Navigate to your ESXi host within vCenter. Go to "Manage" tab and select "Settings" followed by "Advanced System Settings". Look for the settings "Syslog.global.loghost" and highlight this settings. Click the pencil icon to edit the configuration for this setting. 2) You can now add the host name or ip address of your syslog server/s. You can enter just hostname or IP address, use udp://hostname:514 or ssl://hostname:1514 to be more specific on the port and protocol to be used. If you have multiple hosts then you use the comma (,) to separate each server i.e. udp://192.168.0.1:514,udp://192.168.0.2:514 3)We n

Custom ESXi Image - ISO using PowerCLI

There comes a time when you have purchased a new hardware to run your ESXi software and discover that the installable base media provided by VMware does not include the drivers or the drivers are out of date. In the world of Windows (Plug and Play) it would discover the hardware and prompt you to provide the drivers so that Windows would install/update the drivers for the hardware. For ESXi if the drivers are not present during load time then the hardware will possibly not work. VMware uses VIB (vSphere Installation Bundle) as a way for vendors to distribute their drivers. To install these VIBs you can either use Update Manager or command line (esxcli). Now this is all good but it does mean you have to first install the base ESXi then use one of the steps above to install/update the drivers.   Some people might feel that it is OK to update the drivers using the above methods but what if it was the network card that was the new hardware and you needed new drivers. Without the net