* ``409 Conflict`` The request can not be process because of the current status of the instance (sla changed, instance is under deletion, software release can not be changed, ...).
* ``409 Conflict`` The request can not be process because of the current status of the instance
Bang instance
-------------
Trigger the re-instantiation of all partitions in the instance tree
`Request`::
POST http://example.com/api/v1/instance/{instance_id}/bang HTTP/1.1
Content-Type: application/json; charset=utf-8
`Route values`:
* ``instance_id``: the ID of the instance
`Expected Request Body`::
{
"log": "Explain why this method was called",
}
`Expected Response`::
HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
Modifying instance
------------------
Modify the instance information and status.
`Request`::
PUT http://example.com/api/v1/instance/{instance_id} HTTP/1.1
Content-Type: application/json; charset=utf-8
`Expected Request Body`::
{
"status": "started", # one of: started, stopped, updating, error
"log": "explanation of the status",
"connection": {
"custom_connection_parameter_1": "foo",
"custom_connection_parameter_2": "bar"
}
}
Where `status` is required with `log`, `connection` is optional and its existence allow to not send `status` and `log`.
`Expected Response`::
HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
`Error Responses`:
* ``409 Conflict`` The request can not be process because of the current status of the instance (sla changed, instance is under deletion, software release can not be changed, ...).
`Documentation` transaction contains a title, a start_date, a stop_date, a reference, a currency, a payment mode, some categories, some arrows and a list of movement.