Unexpected behaviour on list of environment variables.

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
github-actions
Domain
ci-cd

Research direction

Use the environment example in the issue as the reproduction and trace how the action parses the environment input. Verify how comma-containing AWS_WHITE_LIST values are separated from later variables, then confirm the full example is handled without truncating that value.

Written by the indexing model from the issue text.

Description

So the issue when I trie to provide multiple env vars

environment: ENVIRONMENT=production,AWS_WHITE_LIST=foo.bar,jenkins,bar.baz,baz.foo,DB_NAME=sfasfsf,DB_USERNAME=asdasdasd,SLACK_CHANNEL_ID=QWERTY

On providing AWS_WHITE_LIST it will read only to foo.bar first element, and then it stops and will go to next env var. Escaping. quoting won't work here.

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 DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.