model diff and update only if needed?

Checklist

• I agree to the terms within the OpenFGA Code of Conduct.

Describe the problem you'd like to have solved

Currently it is pretty difficult to manage different versions of models automatically in openfga. For instance, If I add model to my application and always on (kubernetes pod) startup I will "create model" it will create TONS OF different models to database. What I would like to see is that, it could check what is the latest model and apply new model only if needed. Could there be like somekind of mechanism to check is update needed?

It is not really great situation that models needs to be managed manually basically in production environments. Otherwise the database is full of trash.

Describe the ideal solution

I have been thinking way how database migrations are working. Own table which will store the state which version of model is in use and is there newer version available which should be applied.

Is it possible to calculate like checksum for current model and to be applied model? That way we could compare is the model apply needed (perhaps worth of provide functions for that in openfga itself).

Alternatives and current workarounds

No response

Additional context

No response

The issue names no files, tests, or entry points. Start by tracing the existing model-creation and storage flow, then define how model identity or versions should be compared and what tests would demonstrate that unchanged models are not created repeatedly.