According to the documentation users.user should be a valid endpoint?
You certainly can do it with the python APIClient OR through the requests library
I think it is supported only through the API 🙂
Furthermore, when using APIClient() , users is not a valid endpoint at all.
class APIClient(object):
auth = None # type: Any
queues = None # type: Any
tasks = None # type: Any
workers = None # type: Any
events = None # type: Any
models = None # type: Any
projects = None # type: Any
This is taken from clearml/backend_api/session/client/client.py
Is there a way I can do this with the python APIClient or even with the requests library?
$ curl -H "Authorization: Bearer <TOKEN>" -X GET
{"meta":{"id":"ed6c52d030f240a89f001b447ee64a6b","trx":"ed6c52d030f240a89f001b447ee64a6b","endpoint":{"name":"debug.ping","requested_version":"2.26","actual_version":"1.0"},"result_code":200,"result_subcode":0,"result_msg":"OK","error_stack":null,"error_data":{},"alarms":{}},"data":{"msg":"Hello World"}}%
$ curl -H "Authorization: Bearer <TOKEN>" -X GET
{"meta":{"id":"98fb3e83511941fd8d96c518d1c4d153","trx":"98fb3e83511941fd8d96c518d1c4d153","endpoint":{"name":"projects.get_all","requested_version":"2.26","actual_version":"1.0"},"result_code":200,"result_subcode":0,"result_msg":"OK","error_stack":null,"error_data":{},"alarms":{}},"data":...%
$ curl -H "Authorization: Bearer <TOKEN>" -X GET
{"meta":{"id":"48c8eeec8b9d4b13a9add7b7b6828b33","trx":"48c8eeec8b9d4b13a9add7b7b6828b33","endpoint":{"name":"users.user","requested_version":"2.26","actual_version":null},"result_code":404,"result_subcode":0,"result_msg":"Unable to find endpoint for name users.user and version 2.26","error_stack":null,"error_data":{},"alarms":{}},"data":{}}%
Any explanation for why I'm seeing the above behaviour? The debug.ping and projects.get_all endpoints work as expected but the users.user does not work.
Also, regarding the APIClient, it was not designed to facilitate user management or server administration (which is why is does not have these endpoints set)
Is there documentation for this as I was not able to figure this out unfortunately.
This is the definitions section, it describes returned objects, not endpoints
@<1529271085315395584:profile|AmusedCat74> users.user is simply not an endpoint supported by the server 🙂 what you're looking for is users.get_by_id (with the user query field containing the ID)