copilot-cli icon indicating copy to clipboard operation
copilot-cli copied to clipboard

Is copilot-cli still maintained?

Open mattattui opened this issue 1 year ago • 17 comments

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).

mattattui avatar Nov 21 '24 09:11 mattattui

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

ollyw avatar Nov 21 '24 10:11 ollyw

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

  • The AWS Copilot CLI is entering maintenance mode on November 4, 2024, receiving only critical bug fixes and security updates until its end-of-support on February 3, 2025.
  • Existing applications using the AWS Copilot CLI will continue to function as intended unless there is a breaking change to the AWS services it utilizes.
  • After February 3, 2025, the AWS Copilot CLI will no longer receive updates or bug fixes, and its GitHub repository will be archived and made read-only.
  • Users can continue using, accessing, and forking the AWS Copilot CLI on GitHub after the end-of-support date. Feedback can be provided through GitHub discussions or AWS Support channels.

It was announced in #5974, and then walked back in this PR: #5975

  • https://github.com/aws/copilot-cli/pull/5975/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5L7

osterman avatar Nov 21 '24 23:11 osterman

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

ollyw avatar Nov 22 '24 16:11 ollyw

Turns out there is a discussion about this https://github.com/aws/copilot-cli/discussions/5925. I have no idea when the repo doesn't state the status in the readme :man_shrugging:

ollyw avatar Nov 22 '24 18:11 ollyw

Holy crap!

ssyberg avatar Nov 22 '24 20:11 ssyberg

Let's not forget what happened to the previous ECS CLIs.

Spoiler Alert: abandoned.

  • https://github.com/awslabs/fargatecli
  • https://github.com/aws/amazon-ecs-cli

osterman avatar Nov 22 '24 21:11 osterman

Well this is disappointing. This project has helped me a great deal in creating and updating a lot of stacks. I guess I'll have to see after re:Invent what things look like and start a new project coming up with a replacement, but I will have to engineer around the various use cases that it supported (databases, s3, cloudfront, ECS).

Doubt anyone will fork this and take it over, as if you have time to maintain it you probably aren't using the tool anyway.

My ECS dashboard even links to a page about installing the tool at this point, so very odd.

surrealchemist avatar Nov 25 '24 19:11 surrealchemist

Sst could be a potential alternative; its Cluster component can be used to build cluster on ECS fargate. If I start a new project on ECS, I might look into sst

konami99 avatar Nov 28 '24 05:11 konami99

I am looking into CDK again. I wrote a little bit years ago. https://constructs.dev/ might be useful to start with. Its a different kind of workflow, and I will have to brush up on typescript a bit, but its re-usable at least.

Perhaps we will hear some news at re:Invent that might offer some hope.

surrealchemist avatar Dec 02 '24 21:12 surrealchemist

Or Pulumi; I asked Pulumi AI to generate ECS cluster, services and tasks: https://www.pulumi.com/ai/conversations/a29f3cf7-918a-4df2-bf46-219d7175aacc

konami99 avatar Dec 02 '24 22:12 konami99

if this project not gunna be maintained the community should take it over.. theres a lot of good stuff here..

mcam10 avatar Dec 09 '24 19:12 mcam10

This project is very useful to me. Please keep it.

vbarba avatar Jan 23 '25 17:01 vbarba

We're starting a similar project, but with multi-cloud aspirations: https://github.com/serverless/containers

austencollins avatar Feb 12 '25 06:02 austencollins

A “high-performance AI” is needed now more than ever. I am looking for an autonomous AI to maintain AWS Copilot.

iamyukihiro avatar Feb 13 '25 15:02 iamyukihiro

We're starting a similar project, but with multi-cloud aspirations: https://github.com/serverless/containers

Totally unsolicited opinion so feel free to totally ignore me @austencollins but IMHO cloud agnostic has almost no benefit and does incur a steep cost, we abandoned terraform for this very reason. Would love a AWS/ECS specific tool to replace copilot though!

ssyberg avatar Feb 13 '25 15:02 ssyberg