AWS Deprecates CodeCommit(aws.amazon.com)
aws.amazon.com
AWS Deprecates CodeCommit
https://aws.amazon.com/blogs/devops/how-to-migrate-your-aws-codecommit-repository-to-another-git-provider/
6 comments
No surprise here, I wouldn't be surprised to see them deprecate more of the "devops" tools on the platform as they have been frozen in amber for years.
Seems like a better link would be https://repost.aws/questions/QUshILm0xbTjWJZSD8afYVgA/codeco...
They have stopped onboarding new accounts, but from what I can see they don't say anywhere that it is "deprecated" or that it will be shut down in any foreseeable future.
AWS are usually very good in keeping services/features for people already using them, but will stop allowing new users when they don't want to push a service.
They have stopped onboarding new accounts, but from what I can see they don't say anywhere that it is "deprecated" or that it will be shut down in any foreseeable future.
AWS are usually very good in keeping services/features for people already using them, but will stop allowing new users when they don't want to push a service.
"AWS breaking changes and price increases" - https://github.com/SummitRoute/aws_breaking_changes?tab=read...
The source in that link seems to be the same one I linked... Or are you trying to say something else?
The link I posted brings to a list of deprecated functionality and services. Your link is a technote on why no new CodeCommit repos are possible. Not exactly the same?
Do we actually know that it is being deprecated or just stopping the ability to set it up on a new account?
I don't see anything official from AWS stating this. The other link mentions it will still get security fixes but no new features, but no indication of it ever being discontinued.
Is it possible that they simply are working on something new and want to minimize the migration at a later point? (I guess that is still technically deprecating CodeCommit if its something new, but its a difference).
I don't see anything official from AWS stating this. The other link mentions it will still get security fixes but no new features, but no indication of it ever being discontinued.
Is it possible that they simply are working on something new and want to minimize the migration at a later point? (I guess that is still technically deprecating CodeCommit if its something new, but its a difference).
According to this post it looks like new accounts can’t onboard:
https://news.ycombinator.com/item?id=41104997
https://news.ycombinator.com/item?id=41104997
Right I saw that, but no communication about if/when CodeCommit is actually going away.
That is something that AWS tends to be really good on. Maybe a bit uncommitted on smaller features of a product, but this is a weird middleground on an entire product basically that isn't really clear on what the future is.
It doesn't even say "At some point in the future CodeCommit will go away and we will give X amount of notice". Just, no new signups.
That is something that AWS tends to be really good on. Maybe a bit uncommitted on smaller features of a product, but this is a weird middleground on an entire product basically that isn't really clear on what the future is.
It doesn't even say "At some point in the future CodeCommit will go away and we will give X amount of notice". Just, no new signups.
This might be problematic in some use cases.
For example, if a software company works on different products, they would ideally have separate AWS accounts/environments for each product.
If they have established pipelines/infrastructure/procedures/etc., and they use CodeCommit as part of such infrastructure, they won't be able to create a new project, without reworking everything.
For example, if a software company works on different products, they would ideally have separate AWS accounts/environments for each product.
If they have established pipelines/infrastructure/procedures/etc., and they use CodeCommit as part of such infrastructure, they won't be able to create a new project, without reworking everything.
I was honestly wondering about that myself. If in an organization I CodeCommit in use on one account but I need to move over (and for whatever reason moving off of CodeCommit isnt an option at the moment) could this flag be at the organization level or on the account level. Or at the very least an account rep could override since that since I am actually already using it.
I have some personal projects for which I use a Terraform stack to build out a CodeBuild-based pipeline. It was very convenient to create a CodeCommit repo because all of the access could be defined via IAM without the need for any Github Personal Access Tokens. Doesn't seem like I'm in any immediate threat of having to change that, but I guess I'll have to adopt a different strategy for new projects.
"AWS Code Commit Ceased Onboarding New Customers" - 67 comments - https://news.ycombinator.com/item?id=41104997
Nice, less things to learn for getting the AWS certification.