This message was deleted.

sparse-intern-71089

02/04/2020, 6:01 PM

This message was deleted.

gorgeous-egg-16927

02/04/2020, 6:09 PM

You have a couple options here: 1. If you want to reuse the same PVC, you can force a delete-before-replace on the Deployment. https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/pulumi/#CustomResourceOptions-deleteBeforeReplace 2. You could create a

ComponentResource

that wraps the PVC + Deployment so that they’re treated as a unit.

gorgeous-egg-16927

02/04/2020, 6:11 PM

Note that Option 1 will cause some downtime. Here’s an example for Option 2: https://github.com/pulumi/examples/blob/fb5d9bc36d60a4c53e90dc67c3a5d7ec86081010/kubernetes-ts-multicloud/app.ts#L25-L88

❤️ 1

thousands-london-78260

02/04/2020, 6:13 PM

#2 Was a Perfect solution! Thanks…should have know about that feature earlier…going to rewrite my whole infrastructure now 😛

😁 1

gorgeous-egg-16927

02/04/2020, 6:15 PM

That’s one of the primary advantages of using real programming languages with Pulumi — this type of thing is pretty straightforward to express with classes or functions. 🙂

thousands-london-78260

02/04/2020, 6:19 PM

Yeah, I’m from React world…so I had done everything as stateless helper functions. But classes makes way more sense here

thousands-london-78260

02/04/2020, 6:24 PM

One more question @gorgeous-egg-16927, if I do the ComponentResource, and I pass a provider to the super() constructor…does that then set a default provider for any resource that I parent to

this

👍 1

gorgeous-egg-16927

02/04/2020, 6:27 PM

I can’t recall off the top of my head. I think so, but I’ve normally set it explicitly.

2 Views

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.