This message was deleted.

sparse-intern-71089

11/27/2018, 9:57 PM

This message was deleted.

incalculable-sundown-82514

11/27/2018, 10:00 PM

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.

microscopic-florist-22719

11/27/2018, 10:02 PM

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

apply

incalculable-sundown-82514

11/27/2018, 10:02 PM

^ true.

microscopic-florist-22719

11/27/2018, 10:04 PM

you can avoid running the code during a preview by early-returning from the

apply

pulumi.runtime.isDryRun()

true

full-dress-10026

11/27/2018, 10:05 PM

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.

full-dress-10026

11/27/2018, 10:49 PM

If I throw an exception in an

apply

, will the update be cancelled?

microscopic-florist-22719

11/27/2018, 10:50 PM

Yes

microscopic-florist-22719

11/27/2018, 10:51 PM

Any uncaught exception will kill the update

👌 1

full-dress-10026

11/28/2018, 2:06 AM

How would I ensure that my CLI stuff in the

apply

completes before the

pB

Open in Slack

Previous Next

Pulumi Community

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.