Frogbot support for poetry relative dependencies

Hello,

Working on a monorepository:
.
├── services/
│ ├── project1/
│ │ └── pyproject.toml
│ └── project2/
│ └── pyproject.toml
│
├── libs/
│ ├── lib1/
│ │ └── pyproject.toml
│ └── lib2/
│ └── pyproject.toml

toml files have relative dependencies.
(example from a service)
[tool.poetry]
name = "project1"
version = "0.1.0"

[tool.poetry.dependencies]
python = "^3.11"
lib1 = { path = "../../libs/lib1" }

(example from a lib)
[tool.poetry]
name = "lib2"
version = "0.1.0"

[tool.poetry.dependencies]
python = "^3.11"
lib1 = { path = "../lib1" }

The problem (probably):

• frogbot clones the repo into a temporary directory like:
  /builds/<repo>/jfrog.cli.temp-xxxx/
• Inside that temp dir, the relative paths in pyproject.toml (like ../../libs/lib1 or ../lib1) no longer point to the right location.
• Result: Frogbot fails with "path does not exist" when resolving Poetry dependencies.

is there a way to resolve this? am i missing a supported command for poetry?

Start with the services/project1/pyproject.toml and libs/lib2/pyproject.toml examples, then inspect how Frogbot resolves Poetry dependencies after cloning into its temporary directory. Reproduce the path-does-not-exist failure and define done as resolving these relative dependencies correctly in the monorepository layout.