Welcome to the Pulumi community @able-gpu-66623! You should receive a direct message from Greetbot with some considerations about how best to use the community! We'd love to hear more about how you're using Pulumi! - Which language are you using? - Which cloud provider? - How has your experience been so far with Pulumi? You can ask general questions as you undergo your cloud engineering journey in our dedicated #C01PF3E1B8V channel! We're so happy you're here! Let us know how we can help pulumipus flying at rest

• Language: TypeScript & Python • Cloud Provider: AWS, GCP, Azure • Experience: Pretty decent. It has served extremely well, and better than all of the other tools I've used. There are a few quirks worth noting though: ◦ Like most declarative languages refreshing or importing state has been a bit hit or miss. You'd imagine that

pulumi up

,

pulumi refresh

,

pulumi up

would have the second up as a noop, but it often isn't in much the same ways as Terraform has the same problem (probably for the same reason.) ◦ There are some design pattern traps ▪︎ Handling outputs and thinking in terms of stuff happening in the future, not the present is a challenge. ▪︎ There are some unintentional escape hatches that make it more useful than strictly declarative tools like Terraform but also break the purpose of the planner. An easy example is "create a Network Interface, and then for every IP on that network interface create a DNS record. The problem is that the number of IPs is indeterminate at preview time. With Pulumi you can make this work, but doing so causes the preview to mismatch the final behavior since you have to break an unenforced rule about executing creation code inside an apply.