Package com.authzed.api.v1

ReadSchemaRequest returns the schema from the database.

ReadSchemaResponse is the resulting data after having read the Object
Definitions from a Schema.

WriteSchemaRequest is the required data used to "upsert" the Schema of a
Permissions System.

WriteSchemaResponse is the resulting data after having written a Schema to
a Permissions System.

SchemaService implements operations on a Permissions System's Schema.

SchemaService implements operations on a Permissions System's Schema.

SchemaService implements operations on a Permissions System's Schema.

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.

RelationshipFilter is a collection of filters which when applied to a
relationship will return relationships that have exactly matching fields.
resource_type is required. All other fields are optional and if left
unspecified will not filter relationships.

SubjectFilter specifies a filter on the subject of a relationship.
subject_type is required and all other fields are optional, and will not
impose any additional requirements if left unspecified.

ReadRelationshipsRequest specifies one or more filters used to read matching
relationships within the system.

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.

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.
MUST_NOT_MATCH will fail the parent request if any relationships match the
relationships filter.
MUST_MATCH will fail the parent request if there are no
relationships that match the filter.

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.

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.

CheckPermissionRequest issues a check on whether a subject has a permission
or is a member of a relation, on a specific resource.

ExpandPermissionTreeRequest returns a tree representing the expansion of all
relationships found accessible from a permission or relation on a particular
resource.
ExpandPermissionTreeRequest is typically used to determine the full set of
subjects with a permission, along with the relationships that grant said
access.

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.

LookupResourcesResponse contains a single matching resource object ID for the
requested object type, permission, and subject.

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.

LookupSubjectsResponse contains a single matching subject object ID for the
requested subject object type on the permission or relation.

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.

PermissionsService implements a set of RPCs that perform operations on
relationships and permissions.

PermissionsService implements a set of RPCs that perform operations on
relationships and permissions.

PermissionsService implements a set of RPCs that perform operations on
relationships and permissions.

DebugInformation defines debug information returned by an API call in a footer when
requested with a specific debugging header.
The specific debug information returned will depend on the type of the API call made.
See the github.com/authzed/authzed-go project for the specific header and footer names.

CheckDebugTrace is a recursive trace of the requests made for resolving a CheckPermission
API call.

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

ObjectReference is used to refer to a specific object in the system.

ZedToken is used to provide causality metadata between Write and Check
requests.
See the authzed.api.v1.Consistency message for more information.

RelationshipUpdate is used for mutating a single relationship within the
service.
CREATE will create the relationship only if it doesn't exist, and error
otherwise.
TOUCH will upsert the relationship, and will not error if it
already exists.
DELETE will delete the relationship and error if it doesn't
exist.

PermissionRelationshipTree is used for representing a tree of a resource and
its permission relationships with other objects.

AlgebraicSubjectSet is a subject set which is computed based on applying the
specified operation to the operands according to the algebra of sets.
UNION is a logical set containing the subject members from all operands.
INTERSECTION is a logical set containing only the subject members which are
present in all operands.
EXCLUSION is a logical set containing only the subject members which are
present in the first operand, and none of the other operands.

DirectSubjectSet is a subject set which is simply a collection of subjects.