This message was deleted.

sparse-intern-71089

12/01/2022, 6:26 PM

This message was deleted.

little-cartoon-10569

12/01/2022, 7:43 PM

You can use transformations. Or you can use a single opts template object, and customize it for specific resources when necessary.

little-cartoon-10569

12/01/2022, 7:45 PM

The latter is a language-specific solution. It's probably the better option, for languages that make it easy. E.g. in typescript:

Copy code

const baseOpts = { parent: someOtherResource };
...
const resX = new Role("resX", { /* ... */, baseOpts);
const resY = new Bucket("resY", { /* ... */, { ...baseOpts, protect: true });

billowy-army-68599

12/01/2022, 8:48 PM

What’s the opposition to using a component?

gorgeous-architect-28903

12/02/2022, 11:21 AM

Thanks for the suggestions. I did end up using a component in the end, just not in the way I usually do. I have a method now that creates an “empty” component resource instance with the options I want, and returns

pulumi.Parent(res)

-- so now I can do something like:

Copy code

withCluster := withOpts([DependsOn(cluster), provider])
ResourceX(ctx, name, withCluster)
ResourceY(ctx, name, withCluster, anotherOption)

Which at least saves me a bit of typing, and lets me append additional options to the individual resources easily.

3 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.