remove requirement for requirements.txt when specifying dependencies for deploying to functions: support poetry

[brucearctor]

Functions Framework is fantastic! BUT, it looks like there is a requirement to have requirements.txt for dependencies in cloud functions? Is that a functions framework issue? Or a GCP Functions limitation? Ex: would there be somewhere else to take this concern?

Since we generally now use poetry to define our dependencies, that means functions-framework needs a 'special' requirements.txt for dependencies if deploying to GCP Cloud Functions? Is there any known workaround?

Thanks!

[xSAVIKx]

I believe that's a requirement coming from the https://github.com/GoogleCloudPlatform/buildpacks used to build a container image. I'd very much like to see modern tooling support as well.

For those struggling, you can do an export from poetry using the following command: poetry export --no-interaction --without-hashes --format requirements.txt --output requirements.txt

[KaylaNguyen]

Hi, thanks for bringing this to our attention! The solution suggested by @xSAVIKx is a good workaround. We'll file supporting poetry as a feature request for triage.

[brucearctor]

For those struggling, you can do an export from poetry using the following command: poetry export --no-interaction --without-hashes --format requirements.txt --output requirements.txt

yes, that's what I meant by needing a 'special' requrements.txt

Also, would this issue be better filed somewhere else? Ex: does it need to be routed to the functions team?