View All Applied Patches
/paas/api/v1.1/instancemgmt/{identityDomainId}/services/MySQLCS/instances/{serviceId}/patches/applied
Request
-
identityDomainId: string
Name of the identity domain for the MySQL Cloud Service account.
-
serviceId: string
The user-defined name of the Oracle MySQL Cloud Service instance.
-
X-ID-TENANT-NAME: string
Name of the identity domain for the MySQL Cloud Service account.
Response
- application/json
200 Response
array
-
[0]:
object patch-applied-response
Information about an applied patch.
object
-
additionalNote(optional):
string
Free-form text to provide additional information about the patch.
-
appliedBy(optional):
string
Name of the user that applied the patch.
system
displays if the patch was applied by an auto-update scheduled job. -
appliedDate(optional):
string
Date and time that the patch was applied.
-
backupId(optional):
string
Backup ID. You can use the backup ID to manage the backup.
-
backupStatus(optional):
string
Whether a backup of the software was created before the patch was applied. Valid values include:
Available
,SameVersion
,Unavailable
,Unknown
. -
componentPatches(optional):
array componentPatches
Group the details of each patches in the component.
-
currentPatchLevel(optional):
string
Current patch level for the component.
-
displayName(optional):
string
Display name of the patch.
-
id(optional):
integer
Unique ID of the patching operation. Use this ID to get details of a patching operation.
-
inProgress(optional):
boolean
Flag that specifies whether the patch is still in progress.
-
jobId(optional):
string
Job ID for the patch operation.
-
lastStatus(optional):
string
Status of the patch operation. For example:
IN PROGRESS
,COMPLETED
, andFAILED
.COMPLETED_ROLLBACK
is displayed when an applied patch has been rolled back. -
lastStatusMessage(optional):
string
Last message logged for the patch operation.
-
operationType(optional):
string
Patch operating being performed. Valid values include:
Rollback
,Patching
, andNone
. -
patchCategory(optional):
string
Category of the patch. For example:
General
,Multiple
,Security
, and so on. -
patchComponents(optional):
array patchComponents
Group the details of the patch to be applied.
-
patchDescription(optional):
string
Description of the patch.
-
patchId(optional):
string
Patch ID.
-
patchingResult(optional):
object patch-result-info
Groups information about the results of the patch.
-
patchReleaseUrl(optional):
string
URL that provides more information about the patch.
-
patchSeverity(optional):
string
Severity of the patch. For example
Normal
,Mandatory
,Recommended
, and so on. -
patchType(optional):
string
Patch type classification. For example,
Quarterly
,Security
. -
progressMessages(optional):
array progressMessages
List of progress messages for the patch.
-
releaseDate(optional):
string
Date and time patch was released.
-
resultMessage(optional):
string
Patch results message.
-
rollbackId(optional):
string
ID of the rollback that is associated to the completed patching operation. The ID is used to rollback a patch operation.
-
rollbackResult(optional):
object patch-rollback-result
Groups information about the results of the rollback operation. This attribute displays only when a rollback of the patch had been performed.
-
rollbackVersion(optional):
string
Version to which the patched component will be rolled back.
-
totalTime(optional):
string
Duration of the patch operation.
-
toVersion(optional):
string
Version of Oracle MySQL Cloud Service instance that was patched.
array
-
[0]:
object patch-component-details-info
Group the details of each patch in the component.
array
-
[0]:
object patch-component-applied-info
Group the details of the patch to be applied.
object
-
additionalNote(optional):
string
Free-form text to provide additional information about the rollback.
object
-
additionalNote(optional):
string
Free-form text to provide additional information about the rollback.
-
appliedBy(optional):
string
Name of the user that performed the rollback.
-
completeLog(optional):
string
System messages that track the rollback operations.
-
endDate(optional):
string
Date the rollback operation ended.
-
jobId(optional):
string
Job ID for the rollback operation.
-
patchingStatus(optional):
string
Status of the rollback operation. For example,
COMPLETED_ROLLBACK
. -
progressMessages(optional):
array progressMessages
List of progress messages for the rollback.
-
resultMessage(optional):
string
System message that describes the rollback operation.
-
rollbackId(optional):
integer
ID of the rollback operation.
-
startDate(optional):
string
Date and time that the rollback operation started.
object
-
description(optional):
string
Description of the patch.
-
displayName(optional):
string
Display name of the component in this patch.
-
id(optional):
integer
ID of a component patch.
-
preserveFiles(optional):
array preserveFiles
List of files to be preserved during patching.
-
releaseVersion(optional):
string
Release version of the component in this patch.
-
version(optional):
string
Version of the patch component.
-
zipBundles(optional):
array zipBundles
Zips that contain the patched binaries or patches.
array
array
-
[0]:
object patch-zip-bundle-info
Group the details of zips for the patched binaries.
object
-
displayName(optional):
string
Display name of this component.
-
id(optional):
integer
ID of a component patch.
-
md5sum(optional):
string
Checksum used to validate the patch binary.
-
provisioningObjectRef(optional):
string
Location of binary to use when creating a new service instance.
-
releaseDate(optional):
string
Release date of this version.
-
releaseUrl(optional):
string
URL for more information about this release.
-
storageKey(optional):
string
Location of the patch zip on the cloud.
-
zipVersion(optional):
string
Software version that is included in the zip.
object
-
component(optional):
string
Name of the component in this patch. For example,
mysql
. -
id(optional):
integer
ID of a component patch.
-
md5sum(optional):
string
Checksum used to validate the patch binary.
-
patchingObjectRef(optional):
string
Location of binary to use when patching a service instance.
-
preserveFiles(optional):
array preserveFiles
List of files to be preserved during patching.
-
provisioningObjectRef(optional):
string
Location of binary to use when creating a new service instance.
-
version(optional):
string
Version of the patch component.
array
array
Examples
The following example shows how to view a list of applied and rolled back patches by submitting a GET request on the REST endpoint using cURL.
Note: The command in this example uses the URL structure https://rest_server_url/resource-path
, where rest_server_url
is the Oracle Public Cloud or Oracle Cloud Machine REST server to contact for your identity domain or tenant name. See Send Requests for the appropriate URL structure to use on Oracle Public Cloud or Oracle Cloud Machine.
cURL Command
curl -i -X GET \
-u "username:password" \
-H "X-ID-TENANT-NAME: ExampleIdentityDomain" \
-H "Accept: application/json" \
https://rest_server_url/paas/api/v1.1/instancemgmt/ExampleIdentityDomain/services/MySQLCS/instances/MyTestInstance/patches/applied
Example of Response Header
The following shows an example of the response header.
HTTP/1.1 200 OK
Server: Oracle-Application-Server-11g
Content-Language: en
Access-Control-Allow-Headers: Content-Type, api_key, Authorization
Access-Control-Allow-Methods: GET, POST, DELETE, PUT, OPTIONS, HEAD
X-ORACLE-DMS-ECID: 001GtD1d9en6uHFpR0H7id0006BS0002nl
X-ORACLE-DMS-ECID: 001GtD1d9en6uHFpR0H7id0006BS0002nl
Access-Control-Allow-Origin: *
X-Frame-Options: DENY
Content-Type: application/json
Vary: user-agent
Date: Wed, 14 Dec 2016 00:17:04 GMT
Content-Length: 2771
Connection: keep-alive
Example of Response Body
The following shows an example of the response body in JSON format.
[ { "backupStatus": "Available", "additionalNote": "Applying 5.7.16-EE patch as discussed with team on KB-43123.", "appliedBy": "someone@example.org", "appliedDate": "2016-12-13T21:13:16.038+0000", "totalTime": "1 min, 47 sec", "patchId": "5.7.16-EE", "patchDescription": "MySQL Server version 5.7.16", "patchReleaseUrl": "https:\/\/dev.mysql.com\/doc\/relnotes\/mysql\/5.7\/en\/news-5-7-16.html", "releaseDate": "2016-10-12T09:00:00.000+0000", "resultMessage": "MySQL patching succeeded", "lastStatus": "COMPLETED", "lastStatusMessage": "MySQL patching succeeded", "componentPatches": { "mysql": { "id": 1451, "version": "5.7", "releaseVersion": "5.7.16", "displayName": "MySQL Server version 5.7.16", "description": "MySQL Server version 5.7.16", "zipBundles": { "MSAAS": { "id": 1521, "md5sum": "ec434747c1e3d5d0f644ff3d9bd54915", "provisioningObjectRef": "MSCS\/5.7.16\/MySQL_Binaries-5.7.16.zip", "storageKey": "MSCS\/5.7.16\/MySQL_Binaries-5.7.16.zip", "releaseDate": "10\/12\/2016", "releaseUrl": "https:\/\/dev.mysql.com\/doc\/relnotes\/mysql\/5.7\/en\/news-5-7-16.html", "displayName": "MySQL Server version 5.7.16" } }, "preserveFiles": [ ] } }, "patchComponents": [ { "id": 1451, "component": "mysql", "version": "5.7", "md5sum": "ec434747c1e3d5d0f644ff3d9bd54915", "provisioningObjectRef": "MSCS\/5.7.16\/MySQL_Binaries-5.7.16.zip", "patchingObjectRef": "MSCS\/5.7.16\/MySQL_Binaries-5.7.16.zip", "preserveFiles": [ ] } ], "patchType": "Quarterly", "patchCategory": "Upgrade", "patchSeverity": "Normal", "jobId": "4207169", "displayName": "5.7.16", "toVersion": "5.7.16", "inProgress": false, "operationType": "None", "id": 234688, "patchingResult": { "patchingId": 195821, "versionBeforeThisPatch": "mysql 5.7.15", "strategy": "Rolling", "releaseVersionBeforeThisPatch": "5.7.15", "customRollbackId": "4207169_1481663596038", "startDate": "2016-12-13T21:13:16.038+0000", "endDate": "2016-12-13T21:15:04.030+0000", "patchingStatus": "COMPLETED", "resultMessage": "MySQL patching succeeded", "additionalNote": "Applying 5.7.16-EE patch as discussed with team on KB-43123.", "appliedBy": "someone@example.org", "jobId": "4207169", "completeLog": "", "progressMessages": [ "9:13:15.926 PM Phase initialize started", "9:13:16.079 PM Phase initialize completed", "9:13:16.195 PM Phase patch started", "9:13:16.308 PM Phase patch-rex started", "9:15:03.436 PM Phase patch-rex completed", "9:15:03.697 PM Phase patch completed", "9:15:03.814 PM Phase finalize started", "9:15:03.911 PM Completed" ] }, "rollbackId": "234688", "rollbackVersion": "mysql 5.7.15", "currentPatchLevel": "mysql 5.7.16", "progressMessages": [ "9:13:15.926 PM Phase initialize started", "9:13:16.079 PM Phase initialize completed", "9:13:16.195 PM Phase patch started", "9:13:16.308 PM Phase patch-rex started", "9:15:03.436 PM Phase patch-rex completed", "9:15:03.697 PM Phase patch completed", "9:15:03.814 PM Phase finalize started", "9:15:03.911 PM Completed" ] } ]