This message was deleted.
# jobs
s
This message was deleted.
👍 1
b
Just out of curiosity : why would you mix CDK and Pulumi ? Are you happy with CDK v2 so far ?
f
generally speaking we're using CDK when the context is a single AWS account, pulumi if we need to operate across multiple accounts or if we're dealing with non-aws resources
no complaints about CDK v2, not having to constantly import new packages is nice
b
Interesting 🙂 And is CDK better than Pulumi for single account IaC ? Or is that a strategic choice because you believe that CDK isn’t quite on par with Pulumi just yet, but might be in the future ?
f
App teams had a strong preference for CDK, and there's a lot of nice out of the box stuff we get from CDK that isn't available in pulumi (the VPC construct, for example). We're using python, so pulumi crosswalk for AWS wasn't really an option
👍 1
Pulumi was also the riskier/harder to justify option (smaller 3rd party, more questionable long term), scope has been growing slowly/gradually
😕 1
b
CDK is for free, that’s also pretty cool 🙂 Does it have Stack References as well ? TBH I’ve been using Pulumi in Python for years and it works really fine, but I haven’t tried CDK just yet... mostly because it feels like it’s not on the same level as Pulumi just yet
f
To expand on that (and the 😕 ), Pulumi wasn't as widely known. Nobody would question terraform, but pulumi was a lot less widely known
CDK is built on top of Cloudformation, so you get all the same cross stack features + nested stacks