Hi Pulumi team/community! We’re working on bringing full IaC support to our SaaS platform, DevRev — a product-led startup focused on connecting developers and customers. We’ve been experimenting/PoC'ing with dynamic providers, and are now looking to move toward building native providers using the Pulumi Provider SDK (Go). Context & Use Cases We're aiming to support both: • Internal teams managing infrastructure via code (with full versioning, preview, rollback, etc.) • External customers using IaC indirectly to replicate and sandbox configurations between orgs (e.g. prod → staging) Questions we’re trying to answer: 1. OpenAPI support – We have an OpenAPI spec. Can provider code/schemas be generated from it (e.g. via

pulschema

)? How mature is that workflow? 2. YAML support – What’s the best way to allow users to define config in YAML and feed it into native providers/components? 3. Rollback capabilities – If a configuration fails or introduces issues, what built-in mechanisms (or patterns) exist for rolling back to a previous state? 4. Dynamic schemas – Our platform’s schemas are sometimes returned dynamically at runtime. Can Pulumi native providers support this, or would we need to regenerate the provider each time? 5. Multi-language SDKs – Once we have our packaged provider written in Go, what’s the process to generate and distribute SDKs for different languages? How does this work from the standpoint of publishing/distributing to end users (e.g. via npm, PyPI, etc.)? Any advice, resources, or war stories would be hugely appreciated. Thanks in advance!