:wave: Hi everyone, I’m Santiago. I'm new to Pulum...
# getting-started
f
👋 Hi everyone, I’m Santiago. I'm new to Pulumi and have begun reading through docs/building with it. I've already designed and tested a custom proof-of-concept TypeScript dynamic provider to handle resources beyond the core SDK and currently define those resources in TS variables. For my project, I’d love to drive instantiation of that dynamic provider directly from
.yaml
input files—using them as a factory blueprint—so I don’t have to maintain resource definitions in code myself. Right now I’ve cobbled together a custom YAML parser and resource-factory, but I’m concerned about scale and long-term maintainability. So my question would be, does Pulumi offer any built-in support or recommended patterns for mapping Pulumi YAML (or project config) to a TypeScript dynamic provider? If you’ve tackled something similar—or know of component abstractions, or sample repos—I’d greatly appreciate pointers or best-practice examples. Thanks in advance!