## Repository within a repository,

lakectl local checkout/clone

Can a lakeFS repository contain another (or multiple) lakefs repository, tracked with the

*.yaml

file generated by

lakectl local checkout/clone

? I'm looking for a way a repository can "require" other repositories, Similar to a

git submodule

. See the rough attached mermaid diagram for what I'm trying to achieve. This is because I make 3D animations. A 3d model asset often requires a model, which requires a model, which requires a model, and so on. A whole scene typically contains tens or hundreds of models like this, so a dependency tree of models grows. Why can't you use just one repository: I think it is the case that when creating a repository (A), it can contain any set of objects from your object storage (minio in my case) including all the objects from some other repository (B), but not the knowledge that the objects in B make up a repository called B. But next, if you separately update the objects in repo B (check it out > update some files > commit back to B), will A get the updated objects? If my understanding is correct, the answer is no. A would retain the versions it originally pointed to (not my desired behaviour). Leading to the original question above... It is "not my desired behaviour" because (again, if my understanding is correct) in order to update A with a new set of objects from B without knowing that those objects are a collection making up a repository called B, I would have to manually request each object be updated to a new version individually, which would mean manually keeping lists of what objects represented some "module" that I would like to depend on.

Hi @Sam Carter! The use case makes sense but at the moment

lakectl local

has no submodule support. May I ask that you open an issue on GitHub?

Hi @Oz Katz , yes will do 👍🏻, thanks for replying.