port-terraform

Port Terraform provider

Port's Terraform provider (port-labs/port-labs) lets you define blueprints, entities, scorecards, self-service actions, webhooks, and integration mappings as .tf resources, the same way you'd define any other piece of infrastructure. This skill is reference-only: static knowledge about the provider's resource schema, drawn from the current v2.x provider and Port's Terraform docs. It doesn't need a live Port account or Port MCP server to produce correct HCL, only a real account and API credentials to actually terraform apply it.

Out of scope: the underlying Port concepts (property types, relation semantics) are owned by the port-blueprints skill; self-service action JSON schema and invocation method payload templating aren't covered by a skill in this repo yet. This skill only covers how those concepts map onto Terraform arguments. Pulumi is Port's other IaC provider, briefly noted in Step 1, but not covered in depth here.

Prerequisites

• Go over the port-getting-started skill first if this is your first time working with Port.
• The Terraform CLI (or OpenTofu, a drop-in alternative, swap terraform for tofu).
• A Port account and a client_id/client_secret pair, from ... menu > Credentials in the Port app, or the API docs.
• No Port MCP server or CLI is required to write or apply the .tf files this skill produces. If one is connected, use it to check the current live state (list_blueprints) before writing HCL that should match it, and search search_port_knowledge_sources for anything this skill doesn't cover.

Step 1 - Set up the provider

Precondition: no port provider block exists in the working directory yet. Action: add a terraform block pinning port-labs/port-labs, and a provider "port" block with credentials from environment variables, then run terraform init: