Hey all, working on designing repo-level settings in lakeFS. I'm considering using Graveler for versioning, so as to allow a discoverable history of each setting. I was wondering if anyone has thoughts about whether this is possible and how to go about it. The way I see it, if we use the same database schema as the lakeFS installation, we must create new repositories for storing the settings, but those will be visible to the user which may be strange. WDYT?

exposing it to the user as a different repo sounds like a leaky abstraction. What is the benefit of using Graveler? If all we want is a linear audit log - i.e. no branching/diffing/merging - is it worth it?

I agree- I don't suggest exposing it as a different repo, this is something we will have to solve if we decide to go with Graveler. The benefit of using Graveler is basically dogfooding

I see the point, but this is a very simple (simplistic?) use case for it: a single branch, no real merge logic, no branching, tiny repo, so a meta range will include only a single range..