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

Is this project going to supersede the existing CLI tools per AWS service? #31

Closed
sopel opened this issue Jan 10, 2013 · 1 comment
Closed

Comments

@sopel
Copy link

sopel commented Jan 10, 2013

Given its high profile naming/placement/staff, this seems pretty likely/obvious, but I'd appreciate a confirmation, whether the AWS Command Line Interface is indeed intended to supersede the existing CLI tools per AWS service (e.g. the Amazon EC2 API Tools) down the road?

@rbrigham
Copy link

Great question. Having a unified CLI across all AWS services is a high priority for us and is much requested by our customers. Once we reach full service support and match feature parity with the existing CLI tools, then we’ll address ways to help those using the existing CLIs take advantage of the new unified AWS CLI. We’ll tailor the migration approach for each service and its set of customers individually. So the answer is - Yes, in the long term we’d like to align all customers onto our unified AWS CLI, but the migration path and timing for each service is yet to be determined. If you’re already moving your existing CLI scripts to the AWS CLI, then we’d love to hear what parts of that process could be made easier.

gpiccinni pushed a commit to gpiccinni/aws-cli that referenced this issue Nov 3, 2020
kdaily pushed a commit to kdaily/aws-cli that referenced this issue Apr 15, 2021
Integrating Semaphores into Executor
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