POST socket-server/deploy

The last step in a blue/green socket server deployment; switches from the outgoing fleet to the incoming fleet by 'deactivating' the old servers and 'activating' the new ones. (Specifically: the API's understanding of active and inactive.) After this, no new games will be placed on the old servers, and games will start being placed on the new servers.

Example

POST /api/v1/socket-server/deploy HTTP/1.1
Authorization: Signature ...
Content-Type: application/json

{
  "oldServers": [0,1],
  "newServers": [2,3]
}
----------------------------------------
HTTP/1.1 204 No Content
ETag: W/"a-bAsFyilMr4Ra1hIU5PyoyFRunpI"

Security

Authentication is required and restricted to system processes. Requests should be signed using a System key.

URL Parameters

NONE

Request Body

NameDescriptionValue
oldServersthe list of outgoing server IDsarray of number
newServersthe list of incoming server IDsarray of number

Response

Successful responses are code 204. Error responses are standard.

Response Body

NONE