Support for Lambda built-in versions and aliases

Open
#49 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
aws, javascript, node.js
Domain
cli, cloud

Research direction

Start by reading the AWS Lambda versioning and aliases documentation linked in the issue, then inspect node-lambda's deployment entry points for existing version handling. Define the expected command behavior and configuration before making changes; done means the tool can support the requested Lambda versions and aliases with verified behavior.

Written by the indexing model from the issue text.

Description

enhancement hacktoberfest

Hello,

I was wondering if there we're plans to support or migrate to Lambda's official versioning (documented here: http://docs.aws.amazon.com/lambda/latest/dg/versioning-aliases.html).

I'd be happy to implement this and pull-request if it would be useful.

Dominant language
JavaScript
Stars
1.4k
Forks
185
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from motdotla/node-lambda

All issues in motdotla/node-lambda

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.