Travis integration?

Open
#273 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with the package.json and travis.yml examples in the issue, then read the linked Travis Lambda deployment documentation. The issue is a general comparison question rather than a defined code change; it would need a decided scope and an explicit description of what guidance or project documentation should be added before work can be considered done.

Written by the indexing model from the issue text.

Description

question

Just a general question regarding automated deployment of Lambda functions via Travis. I can see a couple of options here:

The first would be to run the node-lambda CLI as an after_success step. For example:

package.json:

{
  "scripts": {
    "deploy": "node-lambda deploy"
  }
}

travis.yml:

after_success:
  - npm run deploy

However, travis also has build in support for Lambda deployment:

e.g.

deploy:
  provider: lambda
  function_name: "lambda-test"
  region: "us-east-1"
  role: "arn:aws:iam::0123456789012:role/lambda_basic_execution"
  runtime: "nodejs4.3"
  handler_name: "handler"
  access_key_id: "AWS ACCESS KEY ID"
  secret_access_key: "AWS SECRET ACCESS KEY"

The only difference I can spot is that Travis doesn't seem to have any options for setting Lambda Environment variables.

Are there any other reasons why it might be better to use node-lambda from a Travis build?

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.