Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow passing a pulumi provider to a cdk resource #61

Open
lukehoban opened this issue Nov 11, 2022 · 2 comments
Open

Allow passing a pulumi provider to a cdk resource #61

lukehoban opened this issue Nov 11, 2022 · 2 comments
Labels
kind/enhancement Improvements or new features

Comments

@lukehoban
Copy link
Member

This was asked in community slack.

I believe there is not currently. All resources are parented to the StackComponent, but that resource is constructed automatically without the end user being able to provide and parameters, including resource options.

The Stack resource that users create does accept an options parameter which is derived from ComponentResourceOptions (and thus supports passing parent and provider), but we don't ultimately pass that through into the Pulumi StackComponent resource. I expect we can and should forward this on to allow the normal inheritance of resource options down into component and it's CDK-based children.

@mnlumi mnlumi added the kind/question Questions about existing features label Jul 21, 2023
@iwahbe iwahbe added kind/enhancement Improvements or new features and removed kind/question Questions about existing features labels Jul 24, 2023
@iwahbe iwahbe changed the title Is there a way to pass a pulumi provider to a cdk resource? Allow passing a pulumi provider to a cdk resource Jul 24, 2023
@t0yv0
Copy link
Member

t0yv0 commented Nov 19, 2024

Tangentially related: #219

@t0yv0
Copy link
Member

t0yv0 commented Nov 19, 2024

CC @flostadler - we might need to revisit design options here (Resource or Stack level).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Improvements or new features
Projects
None yet
Development

No branches or pull requests

4 participants