🚀 Big updates to Pulumi Components! Platform teams can now build powerful infrastructure abstractions in their language of choice, and developers can consume them via simple interfaces—even YAML. It’s a more intuitive, secure way to codify standards while making adoption easy for developers. 🔄 Cross-language consumption – Author in one language, consume in any (including YAML) 📦 Simplified sharing – Push to any git repo to share components ➕ Streamlined usage – Use

pulumi package add <git-url>

to consume 📃 YAML authoring support – Great for teams wanting a simple interface for battle tested components Read the blog: https://www.pulumi.com/blog/pulumi-components Explore the docs: https://www.pulumi.com/docs/iac/concepts/resources/components/

Small one; I think you're missing mentioning

PulumiPlugin.yaml

explicitly in the post 👇

This file tells Pulumi that this directory is a component package that can be consumed across languages (it is not required for a single language component), rather than a standard Pulumi program. In it, you define the language runtime needed to load the plugin:

This is great. I'm fairly new to Pulumi and we have just been improving our codebase using ComponentResources lately. What is the relationship between Pulumi Components and awsx? Is awsx effectively an example of Components?

@able-dusk-25606 thank you for the feedback!! Its fixed now.

This is awesome!