-
Notifications
You must be signed in to change notification settings - Fork 417
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 copilot-cli still maintained? #5987
Comments
I would like to add to this, as we are considering using it on a project, and don't want a dead-end solution. It seems suspiciously quiet on the development front. What is the alternative though? Lightsail is underwhelming and limited. CDK is a bit heavy weight |
On LinkedIn, someone shared a link to this: https://aws.amazon.com/blogs/developer/announcing-end-of-support-for-aws-copilot-cli-effective-february-3-2025/ However, the URL is now a 404. I found this unofficial summary of the link above: https://aws-news.com/article/0192f800-2637-e9e2-b551-bf68f28e1458
It was announced in #5974, and then walked back in this PR: #5975 |
This is not good news. Seems like we can export the CloudFoundation files and create CDK using this https://aws.amazon.com/blogs/devops/announcing-cdk-migrate-a-single-command-to-migrate-to-the-aws-cdk/ However, there is a lot of functionality in copilot that is lost (the easy inspection of status, logs, creation of secrets, best practise creation of multiple resources). It would be REALLY nice to know what Amazon suggest we should migrate to. Amazon projects in this space tend to stagnate (lightsail, copilot, etc). Users don't want to jump to another tool that will obsoleted. Perhaps it is just time to jump ship to Terraform |
Turns out there is a discussion about this #5925. I have no idea when the repo doesn't state the status in the readme 🤷♂️ |
Holy crap! |
Let's not forget what happened to the previous ECS CLIs. Spoiler Alert: abandoned. |
The last release was 1.34.0 in June, 5 months ago. Before that, releases occurred roughly monthly. Release 1.34.0 wasn't documented on the website.
Please let us know if we should be looking to migrate to other solutions, and on what timeline (any suggestions would be extremely welcome).
The text was updated successfully, but these errors were encountered: