REST API - get

vcenter lcm update pending: get

Gets detailed update information.

Request:

HTTP request

GET https://{server}/api/vcenter/lcm/update/pending/{version}

Path Parameters

Name	Type	Description
Required
version	string	A version identified the update.

Response:

HTTP Status Code: 200

Response Body Structure:

{
    "severity" : "CRITICAL",
    "update_type" : "PATCH",
    "pending_update" : "obj-103",
    "release_notes" : [
        "http://myurl.com",
        "http://myurl.com"
    ],
    "release_date" : "2015-01-01T22:13:05.651Z",
    "build" : "string",
    "reboot_required" : true,
    "execute_URL" : "http://myurl.com",
    "description" : "string",
    "category" : "SECURITY",
    "version" : "string"
}

Headers:

None

Type:

Name	Type	Description
bold = required
-	info	A detailed information about the particular vCenter patch/update.
-.description	string	Description of the vSphere update
-.pending_update	string	Identifier of the given vSphere update When clients pass a value of this structure as a parameter, the field must be an identifier for the resource type: `com.vmware.vcenter.lcm.update.pending`. When operations return a value of this structure as a result, the field will be an identifier for the resource type: `com.vmware.vcenter.lcm.update.pending`.
-.version	string	Version of the vSphere update or patch
-.release_date	date_time	Release date of the vSphere update or patch
-.severity	string	Severity of the issues fixed in the vSphere update or patch Level of severity for applying a given patch or update. Value is one of: CRITICAL: Vulnerabilities that can be exploited by an unauthenticated attacker from the Internet or those that break the guest/host Operating System isolation. IMPORTANT: Vulnerabilities that are not rated critical but whose exploitation results in the complete compromise of confidentiality and/or integrity of user data and/or processing resources through user assistance or by authenticated attackers. MODERATE: Vulnerabilities where the ability to exploit is mitigated to a significant degree by configuration or difficulty of exploitation, but in certain deployment scenarios could still lead to the compromise of confidentiality, integrity, or availability of user data and/or processing resources. LOW: All other issues that may or maynot have a security impact. Vulnerabilities where exploitation is believed to be extremely difficult, or where successful exploitation would have minimal impact.
-.build	string	Build number of the vCenter Release
-.update_type	string	Type of the Release based on the current vCenter version Defines update type Value is one of: PATCH: Fixes bugs/vulnerabilities, doesn't change functionality UPDATE: Changes product functionality UPGRADE: Introduces new features, significantly changes product functionality
-.category	string	Category of the release based on features bundled on top of previous release Defines the type of payload this release has on top of previous release Value is one of: SECURITY: Fixes vulnerabilities, doesn't change functionality FIX: Fixes bugs/vulnerabilities, doesn't change functionality UPDATE: Changes product functionality UPGRADE: Introduces new features, significantly changes product functionality
-.reboot_required	boolean	Flag to suggest a reboot after the release is applied
-.execute_URL	URI	VAMI or ISO URL for update or upgrade execute phase redirection
-.release_notes	URI[]	List of URI pointing to patch or update release notes

Errors:

HTTP Status Code	Type	Description
401	unauthenticated	if the user can not be authenticated.
404	not_found	if there is no pending update assosiated with the `version` in the system.
500	error	if there is some unknown internal error. The accompanying error message will give more details about the error.