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

Yeah I think what you are suggesting is probably the best way to do that right now. There is an `--expect-no-changes` flag that you can pass to `preview` command that would fail the command if there were changes. But I don’t think that is too helpful for what you are looking to do perhaps.

A multi-stage pipeline with an approval between a stage with the pulumi task doing `pulumi preview` and a stage with a pulumi task doing the `pulumi up`?

But how does one define the condition that the approval should only be required when there are some changes detected by `pulumi preview`? I already started putting together a solution based on `pulumi preview --json`, might share it if it proves to be stable.