Skip to content
This repository was archived by the owner on Mar 15, 2026. It is now read-only.
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

Closed

Description

@karthich

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.

Activity

  1. karthich commented on Dec 5, 2017

    @karthich
    Author

    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

    -LambdaFunctionFolder1
    
      -service.py	  
    
      -config.yaml
    
    -LambdaFunctionFolder2
    
      -service.py
    
      -config.yaml
    

    -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.

  2. javamonkey79 commented on Feb 13, 2018

    @javamonkey79
    Collaborator

    @karthich yes, please submit a PR

  3. scotwk commented on Feb 23, 2018

    @scotwk

    @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.

  4. karthich commented on Feb 23, 2018

    @karthich
    Author

    Yes. Will submit a PR this weekend. Sorry been super busy at work.

  5. scotwk commented on Feb 23, 2018

    @scotwk

    @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.

  6. karthich commented on Feb 25, 2018

    @karthich
    Author

    If you've already done it locally, I don't want to duplicate your work. Go ahead and submit yours. Thanks!

  7. added a commit that references this issue on Mar 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions