flat-battery-22309
05/20/2025, 3:10 PMpulschema
)? 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!clever-sunset-76585
05/27/2025, 9:54 PMpulschema
and pulumi-provider-framework
. What would you like to know about generating a provider using OpenAPI for your product?
In my opinion, the workflow is mature. If there's something missing, I'd be happy to collaborate with your team to add it.
For your OpenAPI spec, I've drafted a conformance doc to help you get the best results for a provider generated from your API spec: https://github.com/cloudy-sky-software/cloud-provider-api-conformance