`recursive` flag for git based dependencies

[X] I have searched the issues of this repo and believe that this is not a duplicate.
[X] I have searched the FAQ and general documentation and believe that my question is not already covered.

Feature Request

When poetry install a dependency from git, let's say:

requests = { git = "https://github.com/kennethreitz/requests.git", branch = "develop" }

There is no control over the clone command that is being applied when poetry clones this repo. Since poetry supports dependencies from different sources (from local folders, from git repos, from pypi...) there is a specific combination that is not working to me.

Let's say that we have our main repo A. This one depends on a private git repo called B. So far, the pyproject.toml file from A would look like:

# A.pyproject.toml
B = { git = <URL_TO_B>, branch = "develop" }

When we do so, B will be cloned with no --recursive flag. At the same time, if B depends on any git submodules, let's say C, its pyproject.toml would look like this:

# B.pyproject.toml
C = { path = "submodules/C", develop = true }

However, when we perform poetry install on A repository, poetry will clone B in a non recursive way. Therefore B will not be able to install its dependencies as the submodule C will be missing.

As a solution, I would propose two alternative solutions:

Adding recursive keyword to those git-based dependencies
Adding some kind of git_args that would be directly forwarded to the git clone command. This could be helpful not also for the recursive problem but also in case the developer wants to control the cloning depth to reduce installation times.

python-poetry / poetry

`recursive` flag for git based dependencies #8300

Feature Request