This message was deleted.

One option would be to consider moving your db setup logic to out of the “runner” - e.g. the example here provisions a lambda which can be invoked separately or as part of the deploy: https://gist.github.com/lukehoban/5c168258b641368dcccc7810dc454ca9

@sparse-park-68967 Thanks for the example, interesting approach, also seems viable.

https://medium.com/pixel-and-ink/running-database-migrations-in-aws-fargate-with-pulumi-eba56a7bf5e4 This is my approach to DB migrations