dynamic providers / components in pulumi yaml

pulumi / pulumi-yaml

YAML language provider for Pulumi

Apache License 2.0

39 stars 12 forks source link

dynamic providers / components in pulumi yaml #308

Open terekete opened 2 years ago

terekete commented 2 years ago

Hello!

Vote on this issue by adding a 👍 reaction
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

To be able to generate a yaml definition for a pulumi resource based on a custom component or dynamic provider.

Affected area/feature

Flexibility to utilize custom components in yaml.

Frassle commented 2 years ago

I think yaml should already work with multi-language components, same as all our other languages. Like the other languages you can't just call into another language library without it being setup to be called into, i.e. packaged https://www.pulumi.com/docs/guides/pulumi-packages/

AaronFriel commented 2 years ago

@terekete We have an example using Pulumi's EKS provider, which uses custom components written in TypeScript: https://github.com/pulumi/pulumi-yaml/blob/main/examples/aws-eks/Pulumi.yaml

Is that the sort of thing you're referring to or expand on what provider(s) you're trying to use?

terekete commented 2 years ago

Thanks! Did not see this as an option, interesting. So if I read this right. given I can package my component, that can be used by Pulumi YAML, is that correct ?

AaronFriel commented 2 years ago

Yes, that's right. If code generation works for a component provider, that is, it has a valid schema.json, then YAML should be able to use that too. The GetSchema API call must be implemented so that Pulumi YAML can validate the resources & functions created.