Hey all, new to pulumi and also this side of azure — hope asking here is ok. I have a greenfield project at hand and want to implement rigorous continues delivery principles. I’m however new to infrastructure as code (but absolutely love the idea).
• What I am struggling with, is how to deal with the data side of things (replicating data into staging, backups, migration).
• In simple terms, I struggle to wrap my head around my (naive) idea:
◦ create a copy of the production system incl. data, users etc as “test group”
▪︎ apply database migrations / schema changes
▪︎ have tests run in that resource group (which changes data, adds, removes records) and
▪︎ if everything works fine, delete that “testing group”
◦ create a new resource group that again copies from production but only applies schema changes
▪︎ gets promoted to the new production system
◦ the old production system gets destroyed
The stack is “simple”:
Github Actions, Azure PostGres SQL, Codebase pure TypeScript / Node.js / React, Services are maybe Containers with Red Panda (kafka) and Materialize
I’d like to implement this in a deterministic fashion with pulumi 😒weaty-ham: … but really have never pushed CI/CD through to infrastructure before. thank you very much