Cannot use Pipenv with the Pipfile in the relative path.

[takanorig]

Hi,
I use serverless-python-requirements with usePipenv option.
But the modules are not included in the following directory structure.

.
├── functions
│   ├── path
│   │      └── handler.py
│   ├── tests
│   └── serverless.yml
└── Pipfile

serverless.yml

custom:
  pythonRequirements:
    usePipenv: true

Can I set the relative path for Pipfile?

[miketheman]

Hi @takanorig !
The location for the Pipfile is handled by this code:
https://github.com/UnitedIncome/serverless-python-requirements/blob/b6529473c532ece2df36ca05eae27d80a2483967/lib/pipenv.js#L11-L12

The servicePath concept is determined by the serverless framework, so we shouldn't mess with that. We do not have a way today to specifiy the location - it's assumed to be relative and adjacent to serverless.yml

A feature would be needed to inform the configuration where to find the Pipfile - if that's something you're interested in pursuing, please let us know, along with some reasoning about why you've structured your file tree that way.

[takanorig]

Hi, @miketheman.
Thank you for your reply.

I will make the following directory structure,
because I want to deploy the multiple services.

.
├── service-A-functions
│   ├── path
│   │      └── (some lambda functions)
│   ├── tests
│   └── serverless.yml
├── service-B-functions
│   ├── path
│   │      └── (some lambda functions)
│   ├── tests
│   └── serverless.yml
└── Pipfile

I use AWS and the modules defined in Pipfile are the common dependencies.
So I want to deploy them as Lambda Layer.

If I use requirements.txt , it can be specified the location by the "fileName" option.

pythonRequirements:
    fileName: ../requirements.txt

But the "fileName" option cannot be used with "usePipenv" option.

[miketheman]

Thanks for the details!
Looks like this is a feature request to extend the file name configuration to the pipenv (and probably poetry) installation methods. I’ve changed the labels to reflect that.

[jliebrand]

Hi guys - I'm interested in this as well. Is there any update on this?

[jliebrand]

(ps. it seems that creating a hard symbolic link to the root Pipfile works around this... introduces a bit of magic if you will, but might help some)