Is there a way to support transactions,
# spicedb
t
Is there a way to support transactions, or perhaps a way to ask "If I were to add or remove these relationships, now which users have permission?" I'm looking for a way for users to confirm that they actually want the changes they're proposing by showing them a preview of the consequences.
Same with the inverse with Resources.
j
this has been proposed but is right now just an idea
t
Until then, could we use caveats to add relationships with the context of that particular user's session, and then delete them if they change their mind?
j
you could, but I wouldn't really recommend doing so, as the cleanup will be somewhat difficult
t
Hm. Is there fast way to shadow or clone a subset of relationships so we could make the edits against that instead? I know there is a bunch of functionality around testing that I don't quite understand in the code -- is there a way using something like that?
j
there is bulk export/import
but that is to a completely new datastore
t
zed validate doesn't create a completely new datastore, right?
j
it does
in memory
t
... it must isolate whatever runs, and it does clean up afterward, so the main cost seems to be the bulk export/import. Okay. Thanks! If you think of any other ways, let me know. : ) I'll try some things.
2 Views