f3a057eb35
This is the first commit for plugin protocol v6. This is currently unused (dead) code; future commits will add the necessary conversion packages, extend configschema, and modify the providers.Interface. The new plugin protocol includes the following changes: - A new field has been added to Attribute: NestedType. This will be the key new feature in plugin protocol v6 - Several massages were renamed for consistency with the verb-noun pattern seen in _most_ messages. - The prepared_config has been removed from PrepareProviderConfig (renamed ValidateProviderConfig), as it has never been used. - The provisioner service has been removed entirely. This has no impact on built-in provisioners. 3rd party provisioners are not supported by the SDK and are not included in this protocol at all. |
||
|---|---|---|
| .. | ||
| images | ||
| plugin-protocol | ||
| README.md | ||
| architecture.md | ||
| destroying.md | ||
| maintainer-etiquette.md | ||
| resource-instance-change-lifecycle.md | ||
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.)
-
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.
Contribution Guides
- Maintainer Etiquette: guidelines and expectations for those who serve as Pull Request reviewers, issue triagers, etc.