For ELB_LIST

Open
#47 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
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
aws, shell
Domain
cloud, devops

Research direction

Start by locating the ELB_LIST handling and the deployment examples in this CodeDeploy sample repository. Compare how Dev, Staging, and Prod environments are represented, then document whether one branch can deploy across all three without environment-specific configuration; the issue does not name a file or test.

Written by the indexing model from the issue text.

Description

question

I have 3 env Dev Staging and Prod, then in ELB_LIST I have to give all 3 ELB names if I want to use same branch to deploy on all 3 env?

Bit confuse how this can be done without env dependency

Dominant language
Shell
Stars
639
Forks
777
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 aws-samples/aws-codedeploy-samples

All issues in aws-samples/aws-codedeploy-samples

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.