Add Terraform Registry documentation

- docs/index.md - Provider overview and authentication
- docs/resources/power.md - turingpi_power resource
- docs/resources/flash.md - turingpi_flash resource
- docs/resources/node.md - turingpi_node resource

Author: jfreed-dev

docs/index.md

@@ -0,0 +1,69 @@
+---
+page_title: "Turing Pi Provider"
+subcategory: ""
+description: |-
+  Terraform provider for managing Turing Pi 2.5 BMC (Baseboard Management Controller).
+---
+
+# Turing Pi Provider
+
+The Turing Pi provider enables Terraform-based management of [Turing Pi 2.5](https://turingpi.com/) clusters through the BMC (Baseboard Management Controller) API.
+
+## Features
+
+- **Power Management** - Control power state of individual compute nodes
+- **Firmware Flashing** - Flash firmware images to nodes
+- **Boot Verification** - Monitor UART output to verify successful boot
+- **Node Provisioning** - Combined resource for complete node management
+
+## Example Usage
+
+```hcl
+terraform {
+  required_providers {
+    turingpi = {
+      source  = "jfreed-dev/turingpi"
+      version = "1.0.2"
+    }
+  }
+}
+
+provider "turingpi" {
+  username = "root"
+  password = "turing"
+  endpoint = "https://turingpi.local"
+}
+
+resource "turingpi_power" "node1" {
+  node  = 1
+  state = true
+}
+```
+
+## Authentication
+
+The provider requires BMC credentials to authenticate with the Turing Pi board.
+
+### Configuration Options
+
+- `username` - (Required) BMC username. Can also be set via `TURINGPI_USERNAME` environment variable.
+- `password` - (Required) BMC password. Can also be set via `TURINGPI_PASSWORD` environment variable.
+- `endpoint` - (Optional) BMC API endpoint URL. Defaults to `https://turingpi.local`. Can also be set via `TURINGPI_ENDPOINT` environment variable.
+
+### Using Environment Variables
+
+```bash
+export TURINGPI_USERNAME=root
+export TURINGPI_PASSWORD=turing
+export TURINGPI_ENDPOINT=https://192.168.1.100
+```
+
+```hcl
+provider "turingpi" {}
+```
+
+## Resources
+
+- [turingpi_power](resources/power.md) - Control node power state
+- [turingpi_flash](resources/flash.md) - Flash firmware to a node
+- [turingpi_node](resources/node.md) - Comprehensive node management

docs/resources/flash.md

@@ -0,0 +1,55 @@
+---
+page_title: "turingpi_flash Resource - Turing Pi"
+subcategory: ""
+description: |-
+  Flashes firmware to a Turing Pi compute node.
+---
+
+# turingpi_flash (Resource)
+
+Flashes firmware to a Turing Pi compute node. Changes to `node` or `firmware_file` will trigger resource recreation (re-flash).
+
+~> **Note:** Flashing firmware is a destructive operation. Ensure you have the correct firmware file for your compute module.
+
+## Example Usage
+
+```hcl
+resource "turingpi_flash" "node1" {
+  node          = 1
+  firmware_file = "/path/to/firmware.img"
+}
+```
+
+### Using Variables
+
+```hcl
+variable "firmware_path" {
+  description = "Path to the firmware image file"
+  type        = string
+}
+
+resource "turingpi_flash" "node1" {
+  node          = 1
+  firmware_file = var.firmware_path
+}
+
+resource "turingpi_flash" "node2" {
+  node          = 2
+  firmware_file = var.firmware_path
+}
+```
+
+## Argument Reference
+
+- `node` - (Required, Integer, ForceNew) The node ID (1-4). Changing this forces a new resource.
+- `firmware_file` - (Required, String, ForceNew) Path to the firmware image file. Changing this forces a new resource.
+
+## Attribute Reference
+
+In addition to all arguments above, the following attributes are exported:
+
+- `id` - The resource identifier in the format `flash-{node}`.
+
+## Import
+
+Flash resources cannot be imported as they represent a one-time operation.

docs/resources/node.md

@@ -0,0 +1,123 @@
+---
+page_title: "turingpi_node Resource - Turing Pi"
+subcategory: ""
+description: |-
+  Comprehensive management of a Turing Pi compute node including power control, firmware flashing, and boot verification.
+---
+
+# turingpi_node (Resource)
+
+Provides comprehensive management of a Turing Pi compute node, combining power control, firmware flashing, and boot verification into a single resource.
+
+## Example Usage
+
+### Basic Power Control
+
+```hcl
+resource "turingpi_node" "node1" {
+  node        = 1
+  power_state = "on"
+}
+```
+
+### With Firmware Flashing
+
+```hcl
+resource "turingpi_node" "node1" {
+  node          = 1
+  power_state   = "on"
+  firmware_file = "/path/to/firmware.img"
+}
+```
+
+### Full Provisioning with Boot Verification
+
+```hcl
+resource "turingpi_node" "node1" {
+  node                 = 1
+  power_state          = "on"
+  firmware_file        = "/path/to/firmware.img"
+  boot_check           = true
+  login_prompt_timeout = 120
+}
+```
+
+### Complete Cluster Setup
+
+```hcl
+variable "firmware_path" {
+  description = "Path to the firmware image file"
+  type        = string
+  default     = ""
+}
+
+# Node 1 - Full provisioning
+resource "turingpi_node" "node1" {
+  node                 = 1
+  power_state          = "on"
+  firmware_file        = var.firmware_path != "" ? var.firmware_path : null
+  boot_check           = true
+  login_prompt_timeout = 120
+}
+
+# Node 2 - Power on only
+resource "turingpi_node" "node2" {
+  node        = 2
+  power_state = "on"
+  boot_check  = true
+}
+
+# Node 3 - Keep powered off
+resource "turingpi_node" "node3" {
+  node        = 3
+  power_state = "off"
+}
+
+# Node 4 - Quick power on (no boot check)
+resource "turingpi_node" "node4" {
+  node        = 4
+  power_state = "on"
+  boot_check  = false
+}
+
+output "node_status" {
+  value = {
+    node1 = turingpi_node.node1.power_state
+    node2 = turingpi_node.node2.power_state
+    node3 = turingpi_node.node3.power_state
+    node4 = turingpi_node.node4.power_state
+  }
+}
+```
+
+## Argument Reference
+
+- `node` - (Required, Integer) The node ID (1-4).
+- `power_state` - (Optional, String) The desired power state. Valid values are `"on"` or `"off"`. Defaults to `"on"`.
+- `firmware_file` - (Optional, String) Path to the firmware image file. If specified, firmware will be flashed to the node.
+- `boot_check` - (Optional, Boolean) Whether to monitor UART output for login prompt to verify successful boot. Defaults to `false`.
+- `login_prompt_timeout` - (Optional, Integer) Timeout in seconds to wait for login prompt when `boot_check` is enabled. Defaults to `60`.
+
+## Attribute Reference
+
+In addition to all arguments above, the following attributes are exported:
+
+- `id` - The resource identifier in the format `node-{node}`.
+
+## Boot Verification
+
+When `boot_check` is enabled, the provider monitors the node's UART output for a login prompt, indicating the operating system has successfully booted. This is useful for:
+
+- Ensuring firmware flashing completed successfully
+- Waiting for nodes to be ready before dependent operations
+- Detecting boot failures
+
+The `login_prompt_timeout` controls how long to wait for the boot to complete. Increase this value for slower compute modules or complex boot processes.
+
+## Import
+
+Node resources can be imported using the node ID:
+
+```shell
+terraform import turingpi_node.node1 1
+```

docs/resources/power.md

@@ -0,0 +1,45 @@
+---
+page_title: "turingpi_power Resource - Turing Pi"
+subcategory: ""
+description: |-
+  Controls the power state of a Turing Pi compute node.
+---
+
+# turingpi_power (Resource)
+
+Controls the power state of a Turing Pi compute node.
+
+## Example Usage
+
+```hcl
+# Power on node 1
+resource "turingpi_power" "node1" {
+  node  = 1
+  state = true
+}
+
+# Power off node 4
+resource "turingpi_power" "node4" {
+  node  = 4
+  state = false
+}
+```
+
+## Argument Reference
+
+- `node` - (Required, Integer) The node ID (1-4).
+- `state` - (Required, Boolean) The desired power state. `true` for on, `false` for off.
+
+## Attribute Reference
+
+In addition to all arguments above, the following attributes are exported:
+
+- `id` - The resource identifier in the format `power-{node}`.
+
+## Import
+
+Power resources can be imported using the node ID:
+
+```shell
+terraform import turingpi_power.node1 1
+```