BulkExportRelationshipsResponse is one page in a stream of relationship
groups that meet the criteria specified by the originating request. The
server will continue to stream back relationship groups as quickly as it can
until all relationships have been transmitted back.
BulkImportRelationshipsRequest represents one batch of the streaming
BulkImportRelationships API. The maximum size is only limited by the backing
datastore, and optimal size should be determined by the calling client
experimentally.
CheckBulkPermissionsRequest issues a check on whether a subject has permission
or is a member of a relation on a specific resource for each item in the list.
Consistency will define how a request is handled by the backend.
By defining a consistency requirement, and a token at which those
requirements should be applied, where applicable.
ContextualizedCaveat represents a reference to a caveat to be used by caveated relationships.
The context consists of key-value pairs that will be injected at evaluation time.
The keys must match the arguments defined on the caveat in the schema.
DeleteRelationshipsRequest specifies which Relationships should be deleted,
requesting the delete of ALL relationships that match the specified
filters. If the optional_preconditions parameter is included, all of the
specified preconditions must also be satisfied before the delete will be
executed.
ExpandPermissionTreeRequest returns a tree representing the expansion of all
relationships found accessible from a permission or relation on a particular
resource.
LookupResourcesRequest performs a lookup of all resources of a particular
kind on which the subject has the specified permission or the relation in
which the subject exists, streaming back the IDs of those resources.
LookupSubjectsRequest performs a lookup of all subjects of a particular
kind for which the subject has the specified permission or the relation in
which the subject exists, streaming back the IDs of those subjects.
Precondition specifies how and the existence or absence of certain
relationships as expressed through the accompanying filter should affect
whether or not the operation proceeds.
ReadRelationshipsResponse contains a Relationship found that matches the
specified relationship filter(s). A instance of this response message will
be streamed to the client for each relationship found.
Relationship specifies how a resource relates to a subject. Relationships
form the data for the graph over which all permissions questions are
answered.
SubjectReference is used for referring to the subject portion of a
Relationship. The relation component is optional and is used for defining a
sub-relation on the subject, e.g. group:123#members
WatchRequest specifies the object definitions for which we want to start
watching mutations, and an optional start snapshot for when to start
watching.
WatchResponse contains all tuple modification events in ascending
timestamp order, from the requested start snapshot to a snapshot
encoded in the watch response. The client can use the snapshot to resume
watching where the previous watch response left off.
WriteRelationshipsRequest contains a list of Relationship mutations that
should be applied to the service. If the optional_preconditions parameter
is included, all of the specified preconditions must also be satisfied before
the write will be committed.