Skip to content

Commit 0306d77

Browse files
committed
adds optional revision in LookupPermissionSets
After the introduction of BreakingSchemaChange, clients will be notified that an incompatible change has happened and that they need rebuild their index. In order to do that, they need to call LookupPermissionSets with the revision at which the breaking event happened. This introduces an optional revision in LookupPermissionSets to support this use-case.
1 parent 338339b commit 0306d77

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

authzed/api/materialize/v0/watchpermissionsets.proto

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -106,6 +106,10 @@ message LookupPermissionSetsRequest {
106106
// the server will close the stream. If more permission sets are available, the consume should open a new stream
107107
// providing optional_starting_after_cursor, using the cursor from the last response.
108108
uint32 limit = 1;
109+
// optional_at_revision specifies the client is requesting to lookup PermissionSets at a specific revision. It's
110+
// optional, and if not provided, PermissionSets will be looked up at the current revision. The cursor always
111+
// takes precedence in defining the revision when present.
112+
authzed.api.v1.ZedToken optional_at_revision = 2;
109113
// optional_starting_after_cursor is used to specify the offset to start streaming permission sets from.
110114
Cursor optional_starting_after_cursor = 4;
111115
}

0 commit comments

Comments
 (0)