rhythmic-nail-73192
03/16/2021, 5:57 PMbrave-planet-10645
03/16/2021, 7:15 PMmillions-furniture-75402
03/16/2021, 7:34 PMrhythmic-nail-73192
03/16/2021, 7:40 PMinstead telling Pulumi about the resources and then deleting the resource from CFThis is what I mean - running the Pulumi import in a Lambda function as part of the CFN stack update. Yes, you have to be careful with the order of operations (Pulumi import + CFN delete retention + CFN delete)
Alternatively, you could use Pulumi to manage Cloudformation stacks, and migrate stacks into Pulumi over timeTrue, but then - how do we get customers (who run their own AWS accounts in which we have no control) to deploy Pulumi? We'd have to get them to set up a new deployment pipeline, which is too much friction
millions-furniture-75402
03/16/2021, 7:43 PMbrave-planet-10645
03/16/2021, 7:52 PMrhythmic-nail-73192
03/16/2021, 8:12 PMWe've got Pulumi running in a lambda container, so you could do thatAha, excellent. How do you do this? What Lambda environment are you using - do you bring your own docker image or use the standard Python/Go env?
so if there is something that's going to take a while you can separate it outI'm hopeful deployments will be so much faster with Pulumi that 15 minutes will be more than enough 😎 (our nested CFN stacks really slow everything down)