No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

it is not currently possible: <https://github.com/pulumi/pulumi/issues/2318>
terraform is more deterministic and it is easier for a terraform plan to know exactly what is going to be created. pulumi allows for more custom logic which is great for flexibility but makes it harder to be fully deterministic

it is on their "Pulumi Roadmap" as planned though, so it is on their radar

&gt; terraform is more deterministic and it is easier for a terraform plan to know exactly what is going to be created. pulumi allows for more custom logic which is great for flexibility but makes it harder to be fully deterministic
Sorry to "well actually" you, but... well actually, Pulumi is declarative, but you describe the end state using imperative languages.

one of m'colleagues wrote <https://chris.nunciato.org/blog/how-pulumi-is-declarative/|this excellent post> on it

You're correct in saying that we don't have the equivalent to the ability to output the plan in TF, but you can see (in the preview) exactly what you're going to deploy / update / delete

hah! oh yeah agreed - i call pulumi declarative! just the fact that it is possible to perform arbitrary actions in a .Apply makes it so you could write code that is not deterministic, and also hard to serialize into a plan file

when i was first switching from terraform to pulumi, my mental model of how pulumi works was that you use an imperative language to essentially generate your declarative terraform HCL files

'apply' does make supporting something like plan difficult. non-determinism is always bad, but apply is tricky because you could create resources inside apply which it's impossible for the engine to see at preview time.

Thanks for this thread. That blog post was great.