You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 15, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 15, 2026. It is now read-only.
Ability to pass path (relative/absolute) of requirements file #86
My current usage of python-lambda uses a common requirements.txt file for all my lambda functions. Instead of placing the requirements.txt file in the function directory. Can I just add the ability to pass my own requirements.txt file instead of being forced to put the requirements.txt file in the function directory.
@karthich - any work on this? I want something similar. I can submit a PR but I don't want to step on your toes if you have something in progress.
What will the interface look like? afaict the click library doesn't support a parameter with an optional argument, so will --use-requirements be changed to be --requirements PATH? That will break backwards compatibility, but other than that seems to be the right change.
@karthich - I ended up making the changes locally to get stuff going on my end. If you haven't started on it, I'm happy to submit mine. Just let me know.
Activity
karthich commentedon Dec 5, 2017
For context, this is my project structure:
`-LambdaFunctionFolder1
-service.py
-requirements.txt
-config.yaml
-LambdaFunctionFolder2
-service.py
-requirements.txt
-config.yaml`
Instead of that I would like to make the project look like this:
`-Functions
-requirements.txt
`
I am looking at the code and it looks like it should be an easy fix. I can work on this if this is something you guys want added to project.
javamonkey79 commentedon Feb 13, 2018
@karthich yes, please submit a PR
scotwk commentedon Feb 23, 2018
@karthich - any work on this? I want something similar. I can submit a PR but I don't want to step on your toes if you have something in progress.
What will the interface look like? afaict the click library doesn't support a parameter with an optional argument, so will
--use-requirementsbe changed to be--requirements PATH? That will break backwards compatibility, but other than that seems to be the right change.karthich commentedon Feb 23, 2018
Yes. Will submit a PR this weekend. Sorry been super busy at work.
scotwk commentedon Feb 23, 2018
@karthich - I ended up making the changes locally to get stuff going on my end. If you haven't started on it, I'm happy to submit mine. Just let me know.
karthich commentedon Feb 25, 2018
If you've already done it locally, I don't want to duplicate your work. Go ahead and submit yours. Thanks!
Merge pull request #100 from scotwk/feature-specify-requirements-file