Miserlou / Miserlou/lambda-packages
A general question about the limitations of the lambda-packages
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 728
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
As far as I understand, the underlying lambda AMI can change over time. For instance, I expect that there will be libraries and kernel updates, but also distribution updates automatically done by AWS. As opposed with beanstalk, in which one can lock an application to a given Amazon Linux version, that doesn't seem to be the case in Lambda.
Doesn't this mean that precompiled packages can all of the sudden break? Is there a reason for this not to happen that I am not aware of? What is your view on this topic?
Thanks
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
The issue names no files, tests, or entry points. Start by reviewing the project's package-building documentation and AWS Lambda compatibility assumptions. Done would require a maintainer-confirmed explanation of whether AMI changes can break precompiled packages, plus documentation if that behavior needs recording.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- backend, cloud
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100