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.
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.
nerdjon|1 year ago
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.
watermelon0|1 year ago
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.