terraform-provider-restapi
terraform-provider-minio
| terraform-provider-restapi | terraform-provider-minio | |
|---|---|---|
| 5 | 1 | |
| 775 | 11 | |
| 1.0% | - | |
| 6.8 | 0.0 | |
| 15 days ago | over 2 years ago | |
| Go | Go | |
| GNU General Public License v3.0 or later | Mozilla Public License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
terraform-provider-restapi
-
Ask HN: Why is there no Terraform OpenAPI generator?
Hi folks,
My company has an OpenAPI3 spec. We have a community supported Terraform provider that we are moving in-house soon.
I was wondering why there is no easy way to generate a Terraform provider from an OpenAPI spec?
There's no open issue in the generator project[0].
Some googling turned up a couple of projects[1],[2], but they only support Swagger; OpenAPI is the successor to Swagger. There is some progress on supporting OpenAPI[3]. I also found this provider, which is a thin wrapper around REST calls[4].
It's not discussed very much on the Terraform forum[5].
Either I'm missing the need for this or underestimating the difficulty.
0: https://github.com/OpenAPITools/openapi-generator/issues?q=is%3Aissue+is%3Aopen+terraform
1: https://www.logicmonitor.com/blog/how-to-write-a-custom-terraform-provider-automatically-with-openapi
2: https://github.com/dikhan/terraform-provider-openapi
3: https://github.com/dikhan/terraform-provider-openapi/pull/320
4: https://github.com/Mastercard/terraform-provider-restapi
5: https://discuss.hashicorp.com/t/sdk-provider-development-anyone-ever-used-code-generation-or-other-tools-to-simplify-their-provider-development/20301/2
-
Terraform vs. AWS CloudFormation: The Ultimate Comparison
Unless CloudFormation has some way to work with external systems? In my case I wasn't even using a built-in Terraform provider, but a REST API provider which calls our external service's API.
-
Make rest API calls with null_resource?
There is also Mastercard/Rest provider which IMHO results in a bit more natural HCL2 syntax.
-
Terraform Is Not the Golden Hammer
I've used https://github.com/Mastercard/terraform-provider-restapi successfully with a cloud provider which provides a suitable HTTP API. There was a bit of fiddling with JSON formatting and their API docs, but it wasn't too hard all in all.
But like you say - now I've done that, I want to do it for every UI that I'm forced to log in to!
- How automate Fivetran configuration with CI/CD?
terraform-provider-minio
-
Terraform Is Not the Golden Hammer
I recently wrote a very simple custom provider for Minio (the object storage server) in an afternoon. [1]
Getting a functional provider is really not that hard.
But there are indeed a lot of difficulties in dealing with the many edge cases, state divergence, upstream version changes, properly testing everything...
I always prefer to things that have an official Terraform provider.
[1] https://github.com/refaktory/terraform-provider-minio
What are some alternatives?
terraform - Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.
crossplane - The Cloud Native Control Plane
terraform-cdk - Define infrastructure resources using programming constructs and provision them using HashiCorp Terraform
terraform-provider-openapi - OpenAPI Terraform Provider that configures itself at runtime with the resources exposed by the service provider (defined in a swagger file)
openapi-generator - OpenAPI Generator allows generation of API client libraries (SDK generation), server stubs, documentation and configuration automatically given an OpenAPI Spec (v2, v3)