This message was deleted.

sparse-intern-71089

08/29/2019, 6:51 PM

This message was deleted.

gentle-diamond-70147

08/29/2019, 7:03 PM

You can use https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/pulumi/runtime/#isDryRun to only run during the

update

. We don't currently have lifecycle type events that you can hook into.

wide-holiday-59376

08/29/2019, 7:08 PM

I saw you have the concept of custom resources whose providers manage CRUD operations. Is there a way for me to add functions to the existing CRUD operations for an aws instance?

wide-holiday-59376

08/29/2019, 7:08 PM

So that my code would run after-create and before-destroy?

gentle-diamond-70147

08/29/2019, 7:11 PM

No, you can't augment the existing CRUD operations, but you can create your own ComponentResource's.

wide-holiday-59376

08/29/2019, 7:12 PM

Would the ComponentResource be able to differentiate between initial deploy, update of existing server, and destroy?

gentle-diamond-70147

08/29/2019, 7:14 PM

Err... sorry, I think you'll want dynamic provider - that way you can get

create

update

delete

calls. https://www.pulumi.com/docs/intro/concepts/programming-model/#dynamicproviders

wide-holiday-59376

08/29/2019, 7:18 PM

I'll give that a try. So the assumption is that this custom resource will run alongside the server instance and mirror its state?

gentle-diamond-70147

08/29/2019, 7:23 PM

It would be a separate resource with its own state. You can pass other resource outputs into the resource(s) provided by your dynamic provider to "integrate" them.

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.