In-memory Tunables can be manipulated using the endpoint /admin/tunables/. PUT and DELETE
requests to update the Tunables for a given id should be made to /admin/tunables/$id
and have a JSON body in the same format as a Tunable configuration file:
In the case of a PUT, these Tunables will be updated or added for the TunableMap corresponding
to id. Note that this PUT request will *not* cause any existing Tunables to be removed.
In the case of a DELETE, these Tunables will cleared from the TunableMap corresponding
to id. The Tunables are keyed by "id" and "type"; the "value" for each of Tunables to delete
can be any valid value for this Tunable. Because the value of a Tunable is the result of a
composition of TunableMaps (see StandardTunableMap), deleting an in-memory Tunable will cause
the value from the composition of the other TunableMaps to be used.
Linear Supertypes
Service[Request, Response], Closable, (Request) ⇒ Future[Response], AnyRef, Any
In-memory Tunables can be manipulated using the endpoint
/admin/tunables/. PUT and DELETE requests to update the Tunables for a given id should be made to/admin/tunables/$idand have a JSON body in the same format as a Tunable configuration file:{ "tunables": [ { "id" : "$id1", "value" : $value, "type" : "$class" }, { "id" : "$id2", "value" : $value, "type" : "$class" } ] }
In the case of a PUT, these Tunables will be updated or added for the TunableMap corresponding to
id. Note that this PUT request will *not* cause any existing Tunables to be removed.In the case of a DELETE, these Tunables will cleared from the TunableMap corresponding to
id. The Tunables are keyed by "id" and "type"; the "value" for each of Tunables to delete can be any valid value for this Tunable. Because the value of a Tunable is the result of a composition of TunableMaps (see StandardTunableMap), deleting an in-memory Tunable will cause the value from the composition of the other TunableMaps to be used.