opentofu/docs
2023-08-28 14:22:57 +03:00
..
images docs: "Resource Instance Change Lifecycle" revised 2022-06-09 10:19:43 -07:00
plugin-protocol Change terraform doc website links to be a placeholder for now 2023-08-27 15:11:45 +03:00
architecture.md Changes links to internal/terraform in architecture.md 2023-08-28 14:22:57 +03:00
destroying.md Renaming of Terraform to OpenTF 2023-08-22 15:45:05 +03:00
planning-behaviors.md Change terraform doc website links to be a placeholder for now 2023-08-27 15:11:45 +03:00
README.md Change terraform doc website links to be a placeholder for now 2023-08-27 15:11:45 +03:00
resource-instance-change-lifecycle.md Renaming of Terraform to OpenTF 2023-08-22 15:45:05 +03:00
unicode.md Renaming of Terraform to OpenTF 2023-08-22 15:45:05 +03:00

OpenTF Core Codebase Documentation

This directory contains some documentation about the OpenTF Core codebase, aimed at readers who are interested in making code contributions.

If you're looking for information on using OpenTF, please instead refer to the main OpenTF CLI documentation.

OpenTF Core Architecture Documents

  • OpenTF Core Architecture Summary: an overview of the main components of OpenTF Core and how they interact. This is the best starting point if you are diving in to this codebase for the first time.

  • Resource Instance Change Lifecycle: a description of the steps in validating, planning, and applying a change to a resource instance, from the perspective of the provider plugin RPC operations. This may be useful for understanding the various expectations OpenTF enforces about provider behavior, either if you intend to make changes to those behaviors or if you are implementing a new OpenTF plugin SDK and so wish to conform to them.

    (If you are planning to write a new provider using the official SDK then please refer to the Extend documentation instead; it presents similar information from the perspective of the SDK API, rather than the plugin wire protocol.)

  • Plugin Protocol: gRPC/protobuf definitions for the plugin wire protocol and information about its versioning strategy.

    This documentation is for SDK developers, and is not necessary reading for those implementing a provider using the official SDK.

  • How OpenTF Uses Unicode: an overview of the various features of OpenTF that rely on Unicode and how to change those features to adopt new versions of Unicode.

Contribution Guides