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 copilot-cli still maintained? #5987

Open
mattattui opened this issue Nov 21, 2024 · 6 comments
Open

Is copilot-cli still maintained? #5987

mattattui opened this issue Nov 21, 2024 · 6 comments
Labels
type/bug Issues that are bugs.

Comments

@mattattui
Copy link

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 mattattui added the type/bug Issues that are bugs. label Nov 21, 2024
@mattattui mattattui changed the title [Bug]: Is copilot-cli still maintained? Is copilot-cli still maintained? Nov 21, 2024
@ollyw
Copy link

ollyw commented Nov 21, 2024

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

@osterman
Copy link

osterman commented Nov 21, 2024

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

@ollyw
Copy link

ollyw commented Nov 22, 2024

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
Copy link

ollyw commented Nov 22, 2024

Turns out there is a discussion about this #5925. I have no idea when the repo doesn't state the status in the readme 🤷‍♂️

@ssyberg
Copy link

ssyberg commented Nov 22, 2024

Holy crap!

@osterman
Copy link

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

Spoiler Alert: abandoned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Issues that are bugs.
Projects
None yet
Development

No branches or pull requests

4 participants