Terraform Provider Boilerplate.
Start your terraform provider project in seconds with a professional template for building fast, robust, and adaptable terraform providers with a focus on performance and best practices
$ git clone https://github.com/libracoder/terraform-provider-boilerplate.git # Build the provider $ make ARGS="terraform-provider-boilerplate" build // OR $ go build -o terraform-provider-boilerplate # Initialize a working directory containing Terraform configuration files $ terraform init # Create an execution plan. $ terraform plan # Apply the changes required to reach the desired state of the configuration $ terraform apply # Revert changes $ terraform destroy
- Terraform provider should always consume an independent client library or sdk which implements the core logic for communicating with the upstream. You should consider moving the
/sdkto be a separate project.
- Data sources are a special subset of resources which are read-only. They are resolved earlier than regular resources and can be used as part of Terraform’s interpolation.
For transparency into our release cycle and in striving to maintain backward compatibility, terraform-provider-boilerplate is maintained under the Semantic Versioning guidelines and release process is predictable and business-friendly.
See the Releases section of our GitHub project for changelogs for each release version of terraform-provider-boilerplate. It contains summaries of the most noteworthy changes made in each release.
If you have any suggestions, bug reports, or annoyances please report them to our issue tracker at https://github.com/libracoder/terraform-provider-boilerplate/issues
If you discover a security vulnerability within terraform-provider-boilerplate, please send an email to [email protected]
We are an open source, community-driven project so please feel free to join us. see the contributing guidelines for more details.
© 2022, libracoder. Released under MIT License.
terraform-provider-boilerplate is authored and maintained by @libracoder.