undefined | Better HN

0 pointsotterley1mo ago0 comments

> Dependency deadlocks are the big one - you try to share resource attributes (eg ARN) from one stack to another. You remove the consumer and go to deploy again. The producer sees no more dependency so it prunes the export.

I’m a little puzzled. How are you getting dependency deadlocks if you’re not creating circular dependencies?

Also, exports in CloudFormation are explicit. I don’t see how this automatic pruning would occur.

> Deploying certain resources that have names specified (vs generated) often breaks

CDK tries to prevent this antipattern from happening by default. You have to explicitly make it name something. The best practice is to use tags to name things, not resource names.

0 comments

kortex1mo ago

> I’m a little puzzled. How are you getting dependency deadlocks if you’re not creating circular dependencies?

> Also, exports in CloudFormation are explicit. I don’t see how this automatic pruning would occur.

I explained that. It's a quirk of how it tree-shakes, if nothing dereferences the attribute, it deletes the export. And yes it'll automatically create an export if you do something like

    environment={"table": parent_stack.table.table_arn}

> CDK tries to prevent this antipattern from happening by default. You have to explicitly make it name something. The best practice is to use tags to name things, not resource names.

I'm well aware but i'm fighting a ton of institutional inertia at my work.

j / k navigate · click thread line to collapse