Hi! I'm Wall-E, Hardware as a Service (HaaS) for Yandex.Search cluster.
You can read a little about me here. I have a very simple API and it's described below.
Hosts are identified by Inventory number or FQDN.
API usage example:
$ curl -X POST https://$walle_host/v1/get-hosts -H 'Content-Type: application/json' -d '{"names": ["some-host.yandex-team.ru"]}'
$ curl -X GET https://$walle_host/v1/hosts?name=some-host.yandex-team.ru
By default all GET requests return objects with only a few fields set. API clients should specify the exact
fields to return via fields=field1,field2
parameter. If field has no value in
the object, no value will be returned.
GET /path?offset=$offset&limit=$limit
-
traditional paging that returns {"result": objects, "total": total_objects}
object.
GET /path?cursor=$cursor[&limit=$limit]
-
for iteration over all objects where $cursor
points to the object
the search starts from. Returns {"result": objects}
object.
If strict=true
query string parameter is specified, Wall-E will check all query string
parameters for an unknown ones.
You can use Wall-E.Client as a reference implementation of client for Wall-E API.
{{- " | ".join(api_method.methods) + " " -}} {%- if "GET" in api_method.methods -%} {{url_prefix + api_method.uri}} {%- else -%} {{url_prefix + api_method.uri}} {%- endif -%} :
Request query string schema
{{
json.dumps(api_method.query_schema, indent=4, sort_keys=True)|escape|replace("\n", "
"|safe)|safe
}}
Request JSON schema
{{
json.dumps(api_method.json_schema, indent=4, sort_keys=True)|escape|replace("\n", "
"|safe)|safe
}}