You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are use-cases where a developer may want more fine-grain control of the OpenAPI spec generation process, or may want to combine the generator with their own custom Go logic.
Currently, a developer would need to write a tool that interacts with the tfplugingen-openapi CLI directly which currently doesn't expose any information about the process, outside of the resulting provider code spec 😄. The CLI interface was also not designed with this in mind, so it can be cumbersome to implement.
Proposal
Expose a Go module that can be consumed by other developer tools that contains the same logic as the CLI (generating provider code spec, configuring w/ generator config, etc.)
Proposed package design + API is TBD 😄
Additional Information
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Use Cases or Problem Statement
There are use-cases where a developer may want more fine-grain control of the OpenAPI spec generation process, or may want to combine the generator with their own custom Go logic.
Currently, a developer would need to write a tool that interacts with the
tfplugingen-openapi
CLI directly which currently doesn't expose any information about the process, outside of the resulting provider code spec 😄. The CLI interface was also not designed with this in mind, so it can be cumbersome to implement.Proposal
Expose a Go module that can be consumed by other developer tools that contains the same logic as the CLI (generating provider code spec, configuring w/ generator config, etc.)
Additional Information
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: