Lambda Trigger

Open
#143 3 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

The issue names no files, tests, or entry points. Clarify how a trigger list should be represented and how versioned Lambda function names should be handled, then identify the existing deployment configuration path. Done should let users configure multiple versioned triggers without adding each trigger manually in the Lambda dashboard.

Written by the indexing model from the issue text.

Description

enhancement

How to add Lambda Trigger list from this library? Because when I use multiple triggers and lambda function must be versioned by adding version number on lambda function name, I must add one by one again trigger from Lambda Dashboard.

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.