terraform/docs
James Bardin fa1f9be539 add tfplugin proto docs files
Add versioned tfplugin proto files to the docs directory, for easier
reference. The latest version starts as a symlink to the current
file used for generated the tfplugin package in ./internal/tfplugin5.

When changing the protocol version, the old file must be copied to
./docs/plugin-protocol/, and a new symlink created for the latest
version.
2019-06-07 15:47:46 -04:00
..
images docs: Import some existing docs to bootstrap the codebase docs section 2019-03-25 08:01:44 -07:00
plugin-protocol add tfplugin proto docs files 2019-06-07 15:47:46 -04:00
README.md docs: Import some existing docs to bootstrap the codebase docs section 2019-03-25 08:01:44 -07:00
architecture.md docs: Some updates to the architecture summary 2019-03-25 08:01:44 -07:00
maintainer-etiquette.md docs: Import some existing docs to bootstrap the codebase docs section 2019-03-25 08:01:44 -07:00
resource-instance-change-lifecycle.md docs: Import some existing docs to bootstrap the codebase docs section 2019-03-25 08:01:44 -07:00

README.md

Terraform Core Codebase Documentation

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

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

Terraform Core Architecture Documents

  • Terraform Core Architecture Summary: an overview of the main components of Terraform 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 Terraform enforces about provider behavior, either if you intend to make changes to those behaviors or if you are implementing a new Terraform 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.)

Contribution Guides

  • Maintainer Etiquette: guidelines and expectations for those who serve as Pull Request reviewers, issue triagers, etc.