Package: pftel-client
pftel-clientA client library for accessing apfteltelemetry server, typically in the context of ChRIS workflow execution. Most use cases are POSTing log information to the remote server.UsageFirst, create a client:frompftel_clientimportClientclient=Client(base_url="http//your.telemetry.server:22223")Import the models:frompftel_client.modelsimportlog_structured,log_responsefrompftel_client.api.logger_servicesimportlog_write_api_v1_log_postasplogfrompftel_client.typesimportResponseCreate an object with the data to log:d_post:log_structured=log_structured.LogStructured()d_post.log_object='ChRIS_LegMeasurements'd_post.log_collection='run-20230505.1630'd_post.log_event='inference'd_post.app_name='pl-lld_inference'd_post.exec_time=9.4532d_post.payload=''And POST this log to the server:reply:log_response=plog.sync(client=client,json_body=d_post)# or if you need more info (e.g. status_code)reply:Response[log_response]=plog.sync.detailed(client=client,json_body=d_post)Or do the same thing with an async version:reply:log_response=awaitplog.asyncio(client=client,json_body=d_post)# or if you need more info (e.g. status_code)reply:Response[log_response]=awaitplog.asyncio.detailed(client=client,json_body=d_post)By default, when you're calling an HTTPS API it will attempt to verify that SSL is working correctly. Using certificate verification is highly recommended most of the time, but sometimes you may need to authenticate to a server (especially an internal server) using a custom certificate bundle.client=AuthenticatedClient(base_url="https://internal_api.example.com",token="SuperSecretToken",verify_ssl="/path/to/certificate_bundle.pem",)You can also disable certificate validation altogether, but beware thatthis is a security risk.client=AuthenticatedClient(base_url="https://internal_api.example.com",token="SuperSecretToken",verify_ssl=False)There are more settings on the generatedClientclass which let you control more runtime behavior, check out the docstring on that class for more info.Things to know:Every path/method combo becomes a Python module with four functions:sync: Blocking request that returns parsed data (if successful) orNonesync_detailed: Blocking request that always returns aRequest, optionally withparsedset if the request was successful.asyncio: Likesyncbut async instead of blockingasyncio_detailed: Likesync_detailedbut async instead of blockingAll path/query params, and bodies become method arguments.If your endpoint had any tags on it, the first tag will be used as a module name for the function (my_tag above)Any endpoint which did not have a tag will be inpftel_client.api.defaultBuilding / publishing this ClientThis project usesPoetryto manage dependencies  and packaging.  Here are the basics:Update the metadata in pyproject.toml (e.g. authors, version)If you're using a private repository, configure it with Poetrypoetry config repositories.<your-repository-name> <url-to-your-repository>poetry config http-basic.<your-repository-name> <username> <password>Publish the client withpoetry publish --build -r <your-repository-name>or, if for public PyPI, justpoetry publish --buildIf you want to install this client into another project without publishing it (e.g. for development) then:If that projectis using Poetry, you can simply dopoetry add <path-to-this-client>from that projectIf that project is not using Poetry:Build a wheel withpoetry build -f wheelInstall that wheel from the other projectpip install <path-to-wheel>