undefined | Better HN

0 pointsnerdjon1y ago0 comments

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.

0 comments

watermelon01y ago

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.

nerdjonOP1y ago

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.

j / k navigate · click thread line to collapse