-
Notifications
You must be signed in to change notification settings - Fork 440
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
CodeCommit deprecation and alternatives with CodeCatalyst #477
Comments
Source? News? Blog Post? |
Probably referring to this re:Post answer Not seen an official announcement from AWS yet, though. |
Something "more" official https://x.com/jeffbarr/status/1818461689920344321 |
Interesting. They updated the blog post with a disclaimer containing the announcement. (Original Blog Post) On topic: Could AFT support S3 as a possible source for the 4 code repositories?
|
This seems very premature. Codestar Connections makes some bad assumptions about provider operating models, for example requiring an admin PAT to add a Self-Managed GitLab host. Repo owners are unlikely to be Gitlab admins! |
Hi all, thank you for the discussion. AWS CodeCommit is no longer allowing new customers to create repositories. Existing AFT customers with AWS CodeCommit repositories will continue to be supported. Customers with existing repos can also create new repos as needed. |
CodeCommit is being deprecated, and as the default / native option for AFT this has users with infrastructure that will be in need of migration. While other VCS solutions are supported, there is minimal documentation on migration, and minimal documentation on alternatives provided by AWS, such as CodeCatalyst.
The text was updated successfully, but these errors were encountered: