- URL:
- https://<root>/system/deployments/<deploymentID>/refresh
- Methods:
POST- Version Introduced:
- 10.9
Access requirements
Required privileges
The Enterprise Administrator API requires privilege-based access. An administrator must be assigned a specific user privilege, or role, to access any given endpoint. Listed below are the user privileges or roles an administrator can be assigned that provides access to this endpoint. If multiple privileges are listed, only one needs to be assigned to gain access.
Tokens
This API requires token-based authentication. A token is automatically generated for administrators who sign in to the Enterprise Administrator API directory's HTML interface. Tokens generated in this way are stored for the entirety of the session.
Those accessing the API directory outside of the HTML interface will need to acquire a session token from the generate operation in the Enterprise Directory API. For security reasons, all POST requests made to the Enterprise Administrator API must include a token in the request body.
Description
The refresh operation can be used to troubleshoot microservices and pods that may be unresponsive or not functioning as expected. Performing this operation restarts the corresponding pods and re-creates the microservice.
Request parameters
| Parameter | Details |
|---|---|
(Optional) | Introduced at 10.9.1. This parameter specifies whether the operation will run synchronously or asynchronously. If Values: |
| The response format. The default format is Values: |
Example usage
The following is a sample POST request for the refresh operation:
POST /<context>/admin/system/deployments//kvyxph9w5h3o9vgk8dixn/refresh HTTP/1.1
Host: organization.example.com
Content-Type: application/x-www-form-urlencoded
Content-Length: []
async=false&f=pjson&token=-7UDzD6pc1kKKeh2tAj_hrVWtPQyN2LpY7_zteQM754nxrEDTfZr6xBAm9TdwmNP14-WBSVng3PQ6kSiKEyYsIKRaJAktEAuJ47PyLgInSqs3orw9RemsorTu9uvFvJ0q2NExzQz3j3qOgGtJWztTSQArqUonO6gpPGiizXOdVf4wFUlEUA3oUKW9WYO_59UiV27W0SsqIkGIGy2cxCMr7gFv8fbovRkL0NPptnNpt3ppCu-HFO_cZ4m3I7Adcy1JSON Response examples
If async is false, the following response is returned:
{"status": "success"}If async is true, the following response is returned. The value returned for jobs can be used to access the job resource to track a job's status after it's been submitted. For more information, see the Job resource topic.
{
"jobsUrl": "https://organization.example.com/<context>/admin/jobs/ja2ca1a35-881c-400c-a49a-b26883002d6c",
"jobID": "ja2ca1a35-881c-400c-a49a-b26883002d6c",
"jobStatus": "SUBMITTED"
}