Lambda environment variables disappear

Open
#82 2 comments 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
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
aws, github-actions, terraform
Domain
cloud, devops

Research direction

No source files or tests are identified in the issue. Start by reproducing a deployment with the action for the affected application, then compare its Terraform-created environment variables with a repository where the same configuration works. Done means identifying why variables disappear for that application and confirming they persist after deployment.

Written by the indexing model from the issue text.

Description

Last week I noticed that all environment variables disappeared during the deployment using your action, but only for one application code. In other repositories, the same configuration works fine. Any idea what is going on?
I'm using the latest version and not setting any environment variables using the action. All environment variables are created earlier by Terraform.

Dominant language
D2
Stars
435
Forks
57
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 appleboy/lambda-action

All issues in appleboy/lambda-action

Similar issues

More Cloud issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.