terraform-provider-docs
Terraform Provider Documentation Lookup
Why This Skill Exists
Terraform provider APIs have strict argument constraints that are not reliably stored in AI training data. Guessing argument values (port formats, protocol enums, attribute names, etc.) leads to repeated terraform apply failures. Looking up the official docs first saves 5-10 debug cycles.
Real example: alicloud_forward_entry requires port format "1/65535" (slash separator), not "1-65535" (dash). The ip_protocol only accepts any, tcp, udp, forwardgroup — not TCP or UDP. These details are only reliably found in the official docs.
Core Principle
The reason this skill exists is simple: Terraform provider arguments have precise constraints (format strings, enum values, argument interdependencies) that differ between resources even within the same provider. Getting one wrong means a failed terraform apply, reading the error, guessing again, and repeating — often 3-5 times. A single doc lookup before writing the resource eliminates this entire cycle.
Fetch the official documentation page before writing or modifying any Terraform resource or data source. Don't rely on memory or pattern-matching from other resources — each resource has its own unique argument constraints.