4 ms·
Pulumi does not generate a declarative manifest, your infrastructure program runs at the same time as the engine which applies resource operations. This allows
by AaronFriel 4y ago
Pulumi does not generate a declarative manifest, your infrastructure program runs at the same time as the engine which applies resource operations. This allows you to use API calls, sleeps, and so on. It's a much more powerful model, and lets you use arbitrary computations between resources, using the output state of one to make an API call or some side effect, and plumb the result of that into the input of another resource.
Full disclosure: I'm at Pulumi.
- trallnag 4y agoBut Pulumi still uses Terraform providers for many resources? And isn't it just as difficult to have multiple providers that depend on each other in the same stack?
- AaronFriel 4y agoNot exactly, it's a little more nuanced than that. I've done demos using our EKS provider to spin up a cluster, outputting a kubeconfig property and plumbing that into a Kubernetes provider to deploy a Helm chart to the cluster. It's 3 resources and fits on a single screen in most of our languages.
- ragall 4y agoYou call that "powerful", I'd call it a nightmare.
- habitue 4y agoAh, ok my mistake. I was under the impression that Pulumi worked like CDK (except compiled to terraform) and wasn't imperative.