Support for Poetry build tool via JFrog CLI

[earndt-BRONGA]

Is your feature request related to a problem? Please describe.
At present, the JFrog CLI does not natively support attaching build metadata to Python packages built using Poetry in a manner similar to other build tools (consider the --build-name and --build-number options passed to the jfrog rt gradle command.)

Describe the solution you'd like to see
The addition of commands such as jfrog rt poetry and jfrog rt poetry-config isomorphic to those provided for other build tools (e.g. jfrog rt pip, jfrog rt gradle, jfrog rt npm) and subsequent recognition of those commands' by extant JFrog CLI commands (build-publish, build-scan, build-promote &c.)

Describe alternatives you've considered
We've considered converting our existing Poetry projects to Pip, however this is not feasible at this time.

[joergsesterhenn]

We were informed by JFrog Support this is currently planned for 09/2022. Looking forward to being able to use poetry with artifactory/xray.

[joergsesterhenn]

@sverdlov93 @talarian1 is this issue closed with release 2.27.0 ?

[joergsesterhenn]

This still needs at least some documentation here, right?

[eyalbe4]

@joergsesterhenn - although the code that supports Poetry is technically released, the documentation for it is still being worked on. It documentation will become available soon. We'll share an update here when it does.

[eyalbe4]

@joergsesterhenn -
Unfortunately the new build-info functionality we built in JFrog CLI broke following the removal of a file which used to be generated by Poetry. We're trying to get the help of the Poetry Team as you can see in https://github.com/orgs/python-poetry/discussions/6869.

[joergsesterhenn]

Our initial goal was to introduce build-info support for Poetry, but at the end of the development effort, we were forced to stop due to the issue discussed here. As much we want to get back to this (we feel this addition is important), our current focus was shifted to other areas. Hopefully we'll be able to get back to this in the near future.

@eyalbe4 Any idea on when you will be able to look at this again? We curently run an additional pip install of our dependencies just to collect them for xray. That is quite costly and we really want this to be fixed timely.

[ckmeichs]

We are also facing this problem and would be happy about a solution.

[drobert-bfm]

I will add that using pip isn't viable, since pip doesn't respect the lock file. We really need to ensure that the dependency versions listed in the lock file are the ones used for the build-info.

[broglep-work]

What is the current state / stance on supporting poetry? We would like to use JFrog CLI with Poetry

After our initial look at it, it is quite confusing. Official documentation mentions support
for poetry and current version of cli seems to kind of work (we have not fully tested it), but on the other hand poetry example got removed mentioning that it is not supported