is there a path towards utilizing yaml but using custom resources? I really love the yaml experience for end users (engineering teams), but would love to be able to create abstractions for it in the form of ComponentResources in any language

@damp-fall-55922 yes there is. Do have a look at Pulumi Packages: https://www.pulumi.com/blog/pulumiup-pulumi-packages-multi-language-components/ Once you build your abstractions as a Pulumi Package, these can be consumed in any language, including YAML.

Here is one example: EKS package is defined in TypeScript and used in YAML

oh, awesome. I don’t know why I was under the impression that wasn’t possible. is there any info about producing private components, when they’re company-specific?

@damp-fall-55922 you only need to publish the generated packages in a private package repository and you are all set.

how does the pulumi yaml program know where the published packages are? that’s what I’m missing

@agreeable-eye-87399 Looking in the README of one of the YAML examples, it looks like you have to manually install the plugins before running Pulumi: https://github.com/pulumi/examples/tree/master/aws-yaml-static-website

Oh, I don’t think the manual installation is required anymore. Pulumi should install the latest plugin version by default based on the types of your YAML resources.

How does it know where to download the plugin binary from? For instance, how does it know where to look for the pulumiverse/pulumi-astra plugin binary? (Our first published Pulumiverse provider BTW)

That’s a good question - I suspect it defaults to

pulumi

org when searching for a plugin. You would have to specify

pluginDownloadURL

for non-pulumi ones.

Can I specify

pluginDownloadURL

in my YAML program?

Discovery code lives here https://github.com/pulumi/pulumi-yaml/blob/main/pkg/pulumiyaml/packages.go#L113