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

should I just push a preview via API and then review and deploy without Deployment at all?

&gt; I wonder if Deployments and Automation API are compatible?
Both Deployments and Automation API are ways of triggering a `pulumi up` programmatically. They can definitely be used together. We even have <https://github.com/pulumi/automation-api-examples/tree/main/nodejs/remoteDeployment-tsnode|remote automation API> which runs the update via a deployment rather than on the local machine.

&gt; I want to go to Pulumi dashboard, review the changes and deploy it.
You could trigger a preview via the deployments API and then review the output in the Pulumi service console.

We would like to add a deployment approval workflow, which sounds similar to what you're looking for. If you have any ideas or details, we'd really appreciate it if you would open a feature request at <http://github.com/pulumi/service-requests/issues/new|github.com/pulumi/service-requests/issues/new>