Non-secret stuff and .env

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
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 reviewing the node-lambda CLI's existing .env handling and how AWS Lambda environment variables are configured. Define a practical, documented way to commit non-secret values such as AWS_FUNCTION_NAME and AWS_RUNTIME without committing secrets, and verify that the approach works for local runs and deployments.

Written by the indexing model from the issue text.

Description

question

As you shouldn't check in .env, is there a practical way to commit non-secret stuff, like AWS_FUNCTION_NAME, AWS_RUNTIME etc?

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.