Is it possible to clone a Store?

[Valkryst]

I'm attempting to come up with a way to perform large, transactional operations with the OpenFGA API.

For example, I may need to delete and create tens of thousands of relationships within a single transaction. I would like to do this VIA the API, but the Transactional Writes documentation seems to indicate that the API can only handle "...up to 100 unique tuples..." in a single request (transaction).

As an alternative, I thought to:

1. Clone the existing Store, while still allowing access to the original Store.
2. Apply all of the transactional changes to the cloned Store.
3. Swap the cloned store with the original store.
4. Delete the original store.

I think something like this may work, and it would allow me to do a rollback (i.e. delete the cloned store) if something goes wrong, but I don't see an endpoint which would support cloning an existing Store.

Is there a way to accomplish this?

[aaguiarz]

What about cloning your database (backup/restore), and then launch an openfga insance pointing to the cloned db to make the changes?

[Valkryst]

It may be difficult in this situation, though that does sound like it could work.

We're planning for OpenFGA to be deployed alongside our other applications, in potentially isolated customer environments. Accessing those environments may take some escalation/planning, if something were to go wrong.

The backup, restore, and restart would all need to be done automatically and programmatically VIA Java. As far as I'm aware, that is possible to do. However, if any of those operations failed in an unexpected way, then the customer's environment could be rendered unusable until we're granted access to debug and resolve the issue(s).

Compared to calling a single, tested endpoint with well-defined success/failure conditions, it seems a lot riskier