awslabs / awslabs/aws-shell

S3 server side completions don't seem to be working

Open
#71 4 comments 7 reactions 0 assignees View on GitHub
bug
Dominant language
Python
Stars
7.3k
Forks
780
PR merge metrics
No merged PRs in 30d

Description

> e1ven
>
> It says it autocompletes s3 buckets, but it only seemed to using the history, not using a list of accessible buckets. I used s3 ls, and then s3 ls [bucketnames], and s3 ls s3://[bucketnames] and it wasn't autocompleting any of them.
>
> > interpeix
> >
> > I have the same issue, not bucket completion.

[Reddit Source](https://www.reddit.com/r/sysadmin/comments/3x2wns/awsshell_the_official_supercharged_aws_cli/cy14fyu)

Contributor guide

Open the contributing guide

Research direction

Start by reproducing completion for `s3 ls`, `s3 ls [bucketnames]`, and `s3 ls s3://[bucketnames]` with accessible buckets. Trace the S3 completion entry point and compare it with history-based completion; done means accessible bucket names are suggested for these commands.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, python
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.