Skip to main content
The Storage Service moves files between this machine and the platform’s object storage. The API hands out a link and the file travels through it. On most deployments that link is a presigned storage URL, so the bytes never pass through the API. A deployment whose network cannot reach storage serves the link from the API itself instead. Either way, only the resulting reference is sent back to the API. This Service is exposed by the galtea.storage object.
Remember that we will be using the galtea object. More information here.
Most test cases attach files through test_cases.create() or test_cases.upload_input_file(), which call upload() for you. Traces do the same through input_file_paths and output_file_paths on traces.create() and traces.update(). Reach for galtea.storage directly when you need to fetch the bytes back, or upload a file for a purpose other than a test case input or a trace. For the full round trip, from a dataset of documents to a scored answer, see Evaluate Document Inputs.

​
Service Methods