[poetry plugin] enable pyproject-dir to be configurable

[savil]

Summary

We can enable the poetry project to exist in a sub-directory of the devbox-project by allowing a user to set DEVBOX_PYPROJECT_DIR.

Note, this only works if there is a single poetry project in the devbox-project. For multiple poetry projects in a monorepo, I think users may need to define distinct devbox-projects.

Fixes #1563

How was it tested?

In the added example, ran devbox run run_test. Previously, this would fail.

Also verified the default directory is the project dir, by removing the DEVBOX_PYPROJECT_DIR env-var, and seeing this error message:

examples/development/python/poetry/poetry-pyproject-subdir/service> devbox run run_test

Poetry could not find a pyproject.toml file in /Users/savil/code/jetpack/devbox/examples/development/python/poetry/poetry-pyproject-subdir or its parents
Error: error running script "run_test" in Devbox: exit status 1

[savil]

Current dependencies on/for this PR:

• main
  • PR [poetry plugin] enable pyproject-dir to be configurable #1567 👈

This comment was auto-generated by Graphite.

[mikeland73]

I think this is OK, but does it solve the bug in question? I think the user wanted to use this in a multi pyproject repo.

I feel like a better solution is to only run poetry env use if there's a pyproject file

(or maybe a combination of both)

[mikeland73]

this already exists and is called DevboxProjectDir

[savil]

I think this is OK, but does it solve the bug in question? I think the user wanted to use this in a multi pyproject repo.

Yes, it solves it. The user has a single poetry service folder.

[savil]

@mikeland73 I'm not a fan of the conditional check, because then the poetry plugin is less robust. It'll use the python-from-devbox-json in some circumstances and not in others, which could lead to more subtle bugs.