11–16 of 16 posts
Earlier quoted context omitted.
"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?
Earlier quoted context omitted.
According to this post it looks like new accounts can’t onboard: 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…
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.
Earlier quoted context omitted.
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…
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.
Earlier quoted context omitted.
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?
Earlier quoted context omitted.
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?
Right, I was just trying to understand why posting it as a reply to mine, if it was adding context or making a point.