serverless / serverless/serverless
Feature Request: AWS Serverless Application Repository Support
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 46.9k
- Forks
- 5.7k
- Avg merge
- 10h 7m
- Merged PRs (30d)
- 57
Description
Now that AWS Serverless Application Repository Support is in early access, it would make sense to support this.
I would like to continue using sls, but having to convert logic to SAM would make me consider writing it in SAM to begin with.
Maybe it's time to re-consider / prioritise https://github.com/serverless/serverless/issues/2867
Looking forward to feedback here as I need to make some big decisions soon (SAM vs sls)
Contributor guide
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 by reviewing the AWS Serverless Application Repository and the referenced serverless/serverless issue 2867. The issue names no files, tests, or entry points, so first define the supported workflow and acceptance criteria for using sls without converting to SAM. Done would require an agreed implementation scope and validation plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100