A dynamic Terraform provider that auto-configures itself at runtime using OpenAPI/Swagger specifications.
Terraform Provider OpenAPI is a dynamic Terraform provider that configures itself at runtime using OpenAPI/Swagger specifications. It allows service providers to expose their APIs as Terraform resources without writing custom provider code, automatically discovering new API versions and resources. This reduces maintenance overhead and ensures consistency across different APIs.
Service providers and DevOps engineers who manage RESTful APIs and want to expose them as Terraform resources without building custom providers. It's also suitable for teams adopting OpenAPI specifications and seeking automated infrastructure-as-code tooling.
Developers choose this provider because it eliminates the need to write and maintain custom Terraform providers, automatically adapting to API changes. Its dynamic nature reduces manual effort and ensures that Terraform configurations stay in sync with API updates.
OpenAPI Terraform Provider that configures itself at runtime with the resources exposed by the service provider (defined in a swagger file)
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Configures itself at runtime using OpenAPI specs, eliminating manual provider updates as APIs evolve, as highlighted in the overview.
Discovers new API versions and resources without recompilation, reducing maintenance effort for service providers.
Generates Terraform documentation directly from OpenAPI documents, ensuring consistency between specs and user docs.
Supports publishing derived providers to the Terraform Registry, facilitating distribution and adoption.
Requires OpenAPI 2.0 specifications and compliance with specific guidelines, excluding newer OpenAPI 3.0 or custom APIs.
Demands manual installation in Terraform's plugin directory with strict naming conventions, adding setup overhead.
Effectiveness hinges on accurate OpenAPI docs; poor specs can lead to broken Terraform configurations.
Only supports Terraform >= v0.12.0, with older versions needing specific releases, limiting legacy adoption.