1. BC change in APIv2. If the launchedBy property of ServerSummaryDetailsResponse isn't set for the Farm object API method will not provide this property with the response object as it's optional.
2. BC change in APIv2 ScalingConfiguration object. API will always respond with enabled property in the result. Also Scalr has changed error code 'InvalidValue' on 'UnacceptableObjectConfiguration' if ScalingConfiguration.minInstances greater than ScalingConfiguration.maxInstances. Before: HTTP/1.1 400 Bad Request
Server: nginx/1.10.1
Date: Thu, 08 Sep 2016 19:22:24 GMT
Content-Type: application/json; utf-8
Content-Length: 337
Connection: keep-alive
Vary: Accept-Encoding
{
"meta": {
"requestId": "f4412684-ae89-4549-88e3-8683af4875aa"
},
"errors": [{
"code": "InvalidValue",
"message": "Property scaling.maxInstances must be greater than or equal to scaling.minInstances"
}]
} After: HTTP/1.1 422 Unprocessable Entity
Server: nginx/1.10.1
Date: Thu, 08 Sep 2016 19:24:39 GMT
Content-Type: application/json; utf-8
Content-Length: 357
Connection: keep-alive
Vary: Accept-Encoding
{
"meta": {
"requestId": "c1ae9923-1119-4fd2-9e41-03a2335ecd78"
},
"errors": [{
"code": "UnacceptableObjectConfiguration",
"message": "Property scaling.maxInstances must be greater than or equal to scaling.minInstances."
}]
}
3. Scalr's meta-tag v2 has been adjusted with new items.
Before: v2:{SCALR_ENV_ID}:{SCALR_FARM_ID}:{SCALR_FARM_ROLE_ID}:{SCALR_SERVER_ID}:{SCALR_COST_CENTER_ID}:{SCALR_PROJECT_ID} After: v2:{SCALR_ENV_ID}:{SCALR_FARM_ID}:{SCALR_FARM_ROLE_ID}:{SCALR_SERVER_ID}:{SCALR_COST_CENTER_ID}:{SCALR_PROJECT_ID}:{CLOUD_RESOURCE_ID}:{SCALR_ID} |