HTTP/1.1 200 OK
Content-Type: application/json
{
"comment": "",
"created_at": "2020-04-27T19:40:49.000Z",
"customer_id": "x4xCwxxJxGCx123Rx5xTx",
"deleted_at": null,
"id": "SU1Z0isxPaozGVKXdv0eY",
"name": "test-service",
"publish_key": "3c18bd0f5ada8f0cf54724d86c514a8eac4c9b75",
"type": "vcl",
"updated_at": "2020-04-27T19:40:49.000Z",
"versions": [
{
"created_at": "2020-04-09T18:14:30.000Z",
"updated_at": "2020-04-09T18:15:30.000Z",
"deleted_at": null,
"active": true,
"comment": "",
"deployed": true,
"locked": false,
"number": 1,
"staging": false,
"testing": false,
"service_id": "SU1Z0isxPaozGVKXdv0eY"
}
]
}
Removing it does introduce a breaking change. However, any end users rely on the ActiveVersion
field from a Service
would likely be dealing with unexpected behavior in any case. Note that none of the API's service endpoints return a active_version
key in their response. I'd advocate for the field's removal (I did open this issue after all) but I'm curious what the maintainers/community have to say given the breaking change that would be introduced.