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

I think num_workers=0 is part of default configuration for single node
<https://docs.databricks.com/en/clusters/single-node.html>. Also its Databricks API call so I think its not Pulumi starting the cluster but Databricks so I would check their docs.

<https://docs.databricks.com/api/workspace/clusters/create>

Try to specify autoscale, min=max_workers=0?

I don’t see any API to “start” cluster (only restart though) so I think its behavior by design. Asked internally but not sure can get answer quickly

This is the suggestion (but it would not solve the waiting issue I think?)
What will work is to give two consequent API calls: One for creating a new cluster and then one for terminating it right afterwards.
POST /api/2.0/clusters/create
POST /api/2.0/clusters/delete
This will stop the cluster creation