ingoing
« Previous section Next section »
UCloud Developer Guide / Orchestration of Resources / Storage / Provider APIs / Files / Ingoing API
Ingoing API
Table of Contents
Remote Procedure Calls
retrieveProducts
retrieveProducts
Retrieve product support for this provider
Request | Response | Error |
---|---|---|
This endpoint responds with the Product
s supported by this provider along with details for how Product
is supported. The Product
s must be registered with UCloud/Core already.
search
search
Request | Response | Error |
---|---|---|
streamingSearch
streamingSearch
Request | Response | Error |
---|---|---|
browse
browse
Request | Response | Error |
---|---|---|
copy
copy
Request | Response | Error |
---|---|---|
create
create
Request creation of resource.
Request | Response | Error |
---|---|---|
createDownload
createDownload
Request | Response | Error |
---|---|---|
createFolder
createFolder
Request | Response | Error |
---|---|---|
createUpload
createUpload
Request | Response | Error |
---|---|---|
delete
delete
Request deletion of resource.
Request | Response | Error |
---|---|---|
emptyTrash
emptyTrash
Request | Response | Error |
---|---|---|
init
init
Request from the user to (potentially) initialize any resources
Request | Response | Error |
---|---|---|
This request is sent by the client, if the client believes that initialization of resources might be needed. NOTE: This request might be sent even if initialization has already taken place. UCloud/Core does not check if initialization has already taken place, it simply validates the request.
move
move
Request | Response | Error |
---|---|---|
retrieve
retrieve
Request | Response | Error |
---|---|---|
trash
trash
Request | Response | Error |
---|---|---|
updateAcl
updateAcl
Callback received by the Provider when permissions are updated
Request | Response | Error |
---|---|---|
This endpoint is mandatory for Providers to implement. If the Provider does not need to keep internal state, then they may simply ignore this request by responding with 200 OK
. The Provider MUST reply with an OK status. UCloud/Core will fail the request if the Provider does not acknowledge the request.
verify
verify
Invoked by UCloud/Core to trigger verification of a single batch
Request | Response | Error |
---|---|---|
This endpoint is periodically invoked by UCloud/Core for resources which are deemed active. The Provider should immediately determine if these are still valid and recognized by the Provider. If any of the resources are not valid, then the Provider should notify UCloud/Core by issuing an update for each affected resource.
Data Models
FilesProviderStreamingSearchResult
FilesProviderStreamingSearchResult
FilesProviderStreamingSearchResult.EndOfResults
FilesProviderStreamingSearchResult.EndOfResults
FilesProviderStreamingSearchResult.Result
FilesProviderStreamingSearchResult.Result
PartialUFile
PartialUFile
A partial UFile returned by providers and made complete by UCloud/Core
FilesProviderBrowseRequest
FilesProviderBrowseRequest
FilesProviderCopyRequestItem
FilesProviderCopyRequestItem
FilesProviderCreateDownloadRequestItem
FilesProviderCreateDownloadRequestItem
FilesProviderCreateFolderRequestItem
FilesProviderCreateFolderRequestItem
FilesProviderCreateUploadRequestItem
FilesProviderCreateUploadRequestItem
FilesProviderEmptyTrashRequestItem
FilesProviderEmptyTrashRequestItem
FilesProviderMoveRequestItem
FilesProviderMoveRequestItem
FilesProviderRetrieveRequest
FilesProviderRetrieveRequest
FilesProviderSearchRequest
FilesProviderSearchRequest
The base type for requesting paginated content.
Paginated content can be requested with one of the following consistency
guarantees, this greatly changes the semantics of the call:
Consistency | Description |
---|---|
| Consistency is preferred but not required. An inconsistent snapshot might be returned. |
| Consistency is required. A request will fail if consistency is no longer guaranteed. |
The consistency
refers to if collecting all the results via the pagination API are consistent. We consider the results to be consistent if it contains a complete view at some point in time. In practice this means that the results must contain all the items, in the correct order and without duplicates.
If you use the PREFER
consistency then you may receive in-complete results that might appear out-of-order and can contain duplicate items. UCloud will still attempt to serve a snapshot which appears mostly consistent. This is helpful for user-interfaces which do not strictly depend on consistency but would still prefer something which is mostly consistent.
The results might become inconsistent if the client either takes too long, or a service instance goes down while fetching the results. UCloud attempts to keep each next
token alive for at least one minute before invalidating it. This does not mean that a client must collect all results within a minute but rather that they must fetch the next page within a minute of the last page. If this is not feasible and consistency is not required then PREFER
should be used.
📝 NOTE: Services are allowed to ignore extra criteria of the request if the next
token is supplied. This is needed in order to provide a consistent view of the results. Clients should provide the same criterion as they paginate through the results.
FilesProviderStreamingSearchRequest
FilesProviderStreamingSearchRequest
FilesProviderTrashRequestItem
FilesProviderTrashRequestItem
Last updated