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 possible, but in general we don’t have a good solution for this. The main problem is that Pulumi currently doesn’t have a way to “hook in” to another resource’s lifecycle and only run something when a resource is created or replaced. It’s definitely something that we want to do, though, since it’s a killer feature.

FWIW, if the CLI bits you need to run are idempotent, you can work around this limitation using an `apply`

you can avoid running the code during a preview by early-returning from the `apply` if `pulumi.runtime.isDryRun()` is `true`

Hmm, it's not idempotent by default but it might be possible to make it that way. Thanks for the pointers. This feature would indeed be killer.

If I throw an exception in an `apply`, will the update be cancelled?

Any uncaught exception will kill the update

How would I ensure that my CLI stuff in the `apply` completes before the `pB`?