Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Congrats for doing what aws was unable to do! #7

Open
ssbarnea opened this issue Sep 3, 2020 · 1 comment
Open

Congrats for doing what aws was unable to do! #7

ssbarnea opened this issue Sep 3, 2020 · 1 comment

Comments

@ssbarnea
Copy link

ssbarnea commented Sep 3, 2020

You have all the my respect for doing what AWS team failed (or refused to do), regardless what the community asked for.

Reading the aws/aws-cli#4947 is hilarius and uncovered the lack of considerationn from the team "maintaing" the cli tool.

@vemel
Copy link
Collaborator

vemel commented Sep 3, 2020

Thank you @ssbarnea !

Well, there is still a room for improvement.

I mainly built it for CI, because installing AWS CLI v2 in CI is painful. Also, this is the main reason for having --configure command that accepts CLI arguments instead of stdin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants