[BUG] Bad paths in AWSutils.sh --help Output
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 10
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
Currently, AWSutils.sh script's output indicates incorrect installation paths for AWS CLI v1 and v2 command-aliases.
Severity
- Completely Broken (No work-around evident)
- Severely Broken (Work-around possible but difficult)
- Moderately Broken (Trivial work-around)
- Nuisance (Functions but untrapped errors can slip through)
To Reproduce
Steps to reproduce the behavior:
- Execute
AWSutils.sh --help - View output for the
-cand-Cflags - After script has run, find that command-symlinks are elsewhere
Expected behavior
That --help output match script-created configurations
Deviance Description
- v1-CLI is actually installed at
/usr/local/bin/aws1 - v2-CLI is actually installed at
/usr/local/bin/aws2
The --help output says they should be at /usr/local/bin/aws and /usr/bin/aws, respectively
Fix Suggestions
Fix https://github.com/plus3it/AMIgen8/blob/master/AWSutils.sh#L56-L57
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open AWSutils.sh and inspect the help text at lines 56-57, then compare those paths with the script's actual AWS CLI alias locations. Run AWSutils.sh --help before and after the change and verify that the -c and -C descriptions match the created configurations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, shell
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100