Lines Matching full:upload
3 The `sym_upload` tool is able to operate in `sym-upload-v2` protocol mode, in
4 addition to the legacy protocol (which will be referred to as `sym-upload-v1`
5 for the rest of this document). For now `sym-upload-v2` is HTTP/REST-based but
14 * [Serving the `sym-upload-v2` protocol](#serving-the-sym-upload-v2-protocol)
17 * [Upload `create`](#upload-create)
19 * [Upload complete](#upload-complete)
24 Using `sym_upload` in `sym-upload-v2` protocol mode has the following features
25 beyond `sym-upload-v1`:
29 server. If it's present, then the upload is skipped entirely.
37 Uploading in `sym-upload-v2` protocol mode is easy. Invoke `sym_upload` like
39 $ ./sym_upload -p sym-upload-v2 [-k <API-key>] <symbol-file> <API-URL>
43 URL of your `sym-upload-v2` API service (see next section for details), and
51 * Your API's URL was "https://sym-upload-api".
53 * You wanted to upload the symbol file at "path/to/file_name", with
60 $ curl https://sym-upload-api/symbols/file_name/123123123123123123123123123:checkStatus?key=myfancy…
66 $ curl --request POST https://sym-upload-api/uploads:create?key=myfancysecret123
69 Which returns `upload_url` "https://upload-server/42?creds=shhhhh" and
70 `upload_key` "42". Next you upload the file directly like:
72 $ curl -T path/to/file_name "https://upload-server/42?creds=shhhhh"
81 https://sym-upload-api/uploads/42:complete?key=myfancysecret123
84 ### Serving the `sym-upload-v2` Protocol
125 #### Upload `create`
134 to, along with an "upload key" that can be used to notify the service once the
135 file upload is completed. JSON schema:
154 upload endpoint resource and thereby constrain the ability to upload to those
159 Note that the actual symbol upload step is _not_ part of the REST API. The
160 upload URL obtained in the above operation is meant to be used as the endpoint
162 HTTP PUT request is completed use the upload `complete` operation.
164 #### Upload `complete`
196 retrieve a completed upload by its `upload_key`. If the symbol file cannot be