Get desktop application:
View/edit binary Protocol Buffers messages
Unique identifier for the resource - storage id.
Name of the resource.
Architecture of the resource.
List of assigned tags.
User readable message assigned to the upload.
SID or UID (will be interpreted to which based on length)
list of deleted sid's and deleted uids
Name of the resource.
Unique identifer for the resource.
Architecture of the file.
Set of tags the binary needs to have. No TagSet is interpreted as tags undefined, server looks for the default set of tags ("latest"). Empty TagSet is interpreted as no tags specified, server looks for any tag. Specifying a set of tags result in downloading a binary with all the tags specified.
URL for downloading the resource.
Metadata associated with the artifact.
(message has no fields)
Unique identifer for the resource - storage id.
URL for uploading the resource.
It is legal to specify all. The server processes the requests in order. (sets the tags first - if set - adds next, delete last).
Tags to set.
Tags to add.
Tags to del.
(message has no fields)
Metadata associated with an artifact.
Used in: , , , ,
Metadata associated with the equivalent of a file or directory.
Used in:
Semantics of a ListRequest: - each field is an "and". - each field is optional, except for path or uid. - if a set of tags is specified, the item must have all of them. - if a set of tags is not specified, "latest" tag is assumed. - if an empty set of tags is specified, entities with any tag are returned. -> there is no way to query for items with no tags.
Used as request type in: Astore.List
Used as field type in:
optiona, restricts the artifacts to those matching this architecture.
The reason this exists is that proto3 provides no way to test for presence of any fields but messages, and oneof cannot contain repeated fields.
Used in: , ,