Terraform Integration

LimeLink supports managing configuration as infrastructure as code through Terraform. Use this guide as the stable discovery point for the provider documentation shipped with your reviewed LimeLink Terraform release.

Before You Apply

• Create the target Organization and Project in LimeLink.
• Keep LimeLink credentials in your secret manager or Terraform's protected environment configuration.
• Never commit credentials to configuration, state snapshots, plans, logs, prompts, or screenshots.
• Review the provider version and its supported resources before changing production configuration.

Review the Plan

Treat a Terraform plan as a proposed mutation. Confirm that its target Organization and Project, resource ownership, and destructive actions match your intended environment before applying it.

Provider source, version, resource schemas, import behavior, and lifecycle coverage are release-specific. Follow the documentation distributed with the installed provider rather than guessing fields from dashboard labels or public API payloads.

AI-Assisted Workflows

AI coding agents can discover this guide through llms.txt and the MCP Server guide. Generated Terraform still requires human review, version checks, and a saved plan before application.

For direct Link creation from a trusted server, see API Integration. Terraform credentials and public Project UUIDs have different responsibilities; do not place Organization API credentials in mobile applications or prompts.