IntenseWebs/opentofu
3
0
Fork 0
mirror of https://github.com/opentofu/opentofu.git synced 2024-12-30 10:47:14 -06:00
Code Issues Packages Projects Releases Wiki Activity

update some content to reference the extending terraform section

Browse Source
This commit is contained in:
Clint Shryock 2018-07-26 10:26:22 -05:00 committed by Clint
parent c97a4246ff
commit 26b68d98f9
1 changed files with 17 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
website/guides/terraform-provider-development-program.html.md
View File

@ -14,9 +14,9 @@ self-serve, with links to information sources, clearly defined steps, and
checkpoints. checkpoints.
-> **Building your own provider?** If you're building your own provider and -> **Building your own provider?** If you're building your own provider and
aren't interested in having HashiCorp officially approve and regularly test aren't interested in having HashiCorp officially approve and regularly test the
the provider, refer to the provider, refer to the [Writing Custom Providers guide][writing] and the
[Writing Custom Providers guide](/guides/writing-custom-terraform-providers.html). [Extending Terraform][extending] section.
## What is a Terraform Provider? ## What is a Terraform Provider?
@ -89,10 +89,16 @@ language. The
[Writing Custom Providers guide](/guides/writing-custom-terraform-providers.html) [Writing Custom Providers guide](/guides/writing-custom-terraform-providers.html)
is a good resource for developers to begin writing a new provider. is a good resource for developers to begin writing a new provider.
The best approach to building a new provider project is to use the The best approach to building a new provider is to be familiar with both the
[AWS provider](https://github.com/terraform-providers/terraform-provider-aws) [Writing Custom Providers][writing] guide and [Extending Terraform][extending]
as a reference. Given the wide surface area of this provider, almost all section. The guide will give you an introduction in code structure and the
resource types and preferred code constructs are covered in it. basics of authoring a plugin that Terraform can interact with. The Extending
Terraform section contains guides, best practices, and API reference for
developers writing Terraform plugins. Additionally developers are encouraged to
use the [AWS
provider](https://github.com/terraform-providers/terraform-provider-aws) as an
implementation reference. Given the wide surface area of this provider, almost
all resource types and preferred code constructs are covered in it.
It is recommended for vendors to first develop support for one or two resources It is recommended for vendors to first develop support for one or two resources
and go through an initial review cycle before developing the code for the and go through an initial review cycle before developing the code for the
@ -224,3 +230,7 @@ in the section above.
## Contact Us ## Contact Us
For any questions or feedback please contact us at <terraform-provider-dev@hashicorp.com>. For any questions or feedback please contact us at <terraform-provider-dev@hashicorp.com>.
[writing]: /guides/writing-custom-terraform-providers.html
[extending]: /docs/extend/index.html