serverless / serverless/serverless
Ability to pick lambda version or aliases in api gateway configuration (function.name.events.http)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 46.9k
- Forks
- 5.7k
- Avg merge
- 10h 7m
- Merged PRs (30d)
- 57
Description
Feature Proposal
Description
I think it would be useful to have ability to specify lambda version or aliases in api gateway configuration. As a use case consider situation when lambda have non backward compatible changes in request/response structure.
How about new attributes version and alias under functions.{name}.events.http, so it would look like this:
functions:
execute:
handler: src.execute_model.lambda_handler
description: Execute model
events:
- http:
path: /api/v1/model
version: 1
method: POST
- http:
path: /api/v2/model
method: POST
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
No files or tests are named. Start by tracing how HTTP events are configured for AWS API Gateway, then determine how the requested version and alias attributes should be represented and validated; done means both attributes can select the Lambda version or alias for an HTTP event without changing existing configurations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript
- Domain
- api, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100