Deployment SLAs

Deployment scales are singular resources: you only have one scale per service. Deleting a scale is not a meaningful action. Read about using deployments and using scales.

Actions

• Get - return details of a specific deployment SLA
• Create - create or update a specific deployment SLA
• Delete - delete a deployment SLA

Get single deployment SLA

Return details for a specific SLA that’s part of a specific cluster.

Request

• GET
• /api/v1/deployments/{deployment_name}/clusters/{cluster_name}/sla
• The request body should be empty.

Response

If successful, will return the specified SLA resource in the specified accept format (default JSON).

Errors

• The requested resource could not be found.

Create deployment SLA

Create or update a specific deployment SLA.

Request

• PUT
• /api/v1/deployments/{deployment_name}/clusters/{cluster_name}/sla
• The request body should include at least the minimum SLA resource in the specified content-type format (default JSON).

Response

If successful, will return the updated deployment resource in the specified content-type format (default JSON).

Delete deployment SLA

Delete an SLA from a running deployment. Note that delete operations are idempotent: sending a second request with the same content will not result in an error response (4xx).

Request

• DELETE
• /api/v1/deployments/{deployment_name}/clusters/{cluster_name}/services/{service_name}/scale
• The request body should be empty.

Response

A successful delete operation has status code 204 No Content or 202 Accepted with an empty response body.

Last updated on December 6, 2017