-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Comments
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. |
Integrating Semaphores into Executor
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?
The text was updated successfully, but these errors were encountered: