Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
70a1f13 to
04edffb
Compare
pages/spicedb/concepts/commands.mdx
Outdated
| | --migration-backfill-batch-size | number of items to migrate per iteration of a datastore backfill (default 1000) | | | ||
| | --migration-timeout | defines a timeout for the execution of the migration, set to 1 hour by default (default 1h0m0s) | | | ||
| | --migration-backfill-batch-size | number of items to migrate per iteration of a datastore backfill | 1000 | | ||
| | --migration-timeout | defines a timeout for the execution of the migration | 1h | |
There was a problem hiding this comment.
These are copied from the output of spicedb serve --help - I'd recommend either leaving them as-is or fixing them in the upstream as well.
There was a problem hiding this comment.
Are they copied manually every time the upstream changes or is there an automated process?
There was a problem hiding this comment.
😅 I think it's a manual process and I don't know that it's been done after every release. We've got work that a community member has contributed to autogenerate docs for zed and SpiceDB in flight, but it isn't currently working. I've got it somewhere on my list to figure out...
There was a problem hiding this comment.
Ok, undid all the changes in this file.
04edffb to
2f4e7a4
Compare
2f4e7a4 to
629dfb7
Compare
629dfb7 to
169a4b8
Compare
169a4b8 to
427c3cb
Compare
|
|
||
| Within a Permissions System, a [CheckPermission] call is always made between an object representing the *resource* and an object representing a *subject*: The API call returns whether the *subject* has the specified permission on the *resource*. | ||
|
|
||
| The choice of how to represent subjects can have large downstream effects on the design of a permissions system. |
There was a problem hiding this comment.
This message is repeated in line 21
| In the example below, the schema enforces the following authorization logic: a user can only view a document if the user is related to the document as viewer and editing is enabled for the document. | ||
| To enable document editing in the example below, you need to establish a wildcard relationship that connects all users to the document using the ```edit_enabled``` wildcard relation. | ||
| A user will have ```edit``` permission on the document if they are related to the document as an ```editor``` and they relate to the document through ```edit_enabled```. | ||
| In the example below, the schema enforces the following authorization logic: a user will have ```edit``` permission on the document if they are related to the document as an ```editor``` and they relate to the document through ```edit_enabled```. |
There was a problem hiding this comment.
I've never seen inlined-triple-backtick. does it differ from single backtick?
I guess you're cribbing from what's around it 🤔
| This command will also highlight which parts of the traversal were cached and if a cycle is detected. | ||
| This command will also highlight which parts of the traversal were cached and if a [cycle] is detected. | ||
|
|
||
| [cycle]: ./recursion-and-max-depth#recursion-in-relationships |
No description provided.