Miserlou / Miserlou/lambda-packages
Proposal: Automatic Package Compilation
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 728
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
In some sense, the package compilation for AWS Lambda it's simple, following some basic steps, described in the README for example, where you should install the package dependencies and then compile, zip, and PR.
It's possible to make this process automatic using a tool like Travis? Otherwise, I can make available an instance on EC2 running the correct AMI to that purposes, where should have some listener (Flask for example) that runs the process.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the package compilation steps described in the README and determine what parts of the current process would need automation. Compare the proposed Travis-based workflow with the alternative EC2 listener approach; done would require an agreed design and an automated compilation path for the packages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, flask, python
- Domain
- build-system, cloud, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100