terraform-search-import

Descubre recursos existentes en la nube utilizando consultas de Terraform Search e impórtalos de forma masiva a la gestión de Terraform. Úsalo al incorporar infraestructura no gestionada…

npx skills add https://github.com/hashicorp/agent-skills --skill terraform-search-import

Terraform Search and Bulk Import

Discover existing cloud resources using declarative queries and generate configuration for bulk import into Terraform state.

References:

When to Use

  • Bringing unmanaged resources under Terraform control
  • Auditing existing cloud infrastructure
  • Migrating from manual provisioning to IaC
  • Discovering resources across multiple regions/accounts

IMPORTANT: Check Provider Support First

BEFORE starting, you MUST verify the target resource type is supported:

# Check what list resources are available
./scripts/list_resources.sh aws      # Specific provider
./scripts/list_resources.sh          # All configured providers

Decision Tree

  1. Identify target resource type (e.g., aws_s3_bucket, aws_instance)

  2. Check if supported: Run ./scripts/list_resources.sh <provider>

  3. Choose workflow:

    • ** If supported**: Check for terraform version available.
    • ** If terraform version is above 1.14.0** Use Terraform Search workflow (below)
    • ** If not supported or terraform version is below 1.14.0 **: Use Manual Discovery workflow (see references/MANUAL-IMPORT.md)

    Note: The list of supported resources is rapidly expanding. Always verify current support before using manual import.

Prerequisites

Before writing queries, verify the provider supports list resources for your target resource type.

Discover Available List Resources

Run the helper script to extract supported list resources from your provider:

# From a directory with provider configuration (runs terraform init if needed)
./scripts/list_resources.sh aws      # Specific provider
./scripts/list_resources.sh          # All configured providers

Or manually query the provider schema:

terraform providers schema -json | jq '.provider_schemas | to_entries | map({key: (.key | split("/")[-1]), value: (.value.list_resource_schemas // {} | keys)})'

Terraform Search requires an initialized working directory. Ensure you have a configuration with the required provider before running queries:

# terraform.tf
terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "~> 6.0"
    }
  }
}

Run terraform init to download the provider, then proceed with queries.

Terraform Search Workflow (Supported Resources Only)

  1. Create .tfquery.hcl files with list blocks defining search queries
  2. Run terraform query to discover matching resources
  3. Generate configuration with -generate-config-out=<file>
  4. Review and refine generated resource and import blocks
  5. Run terraform plan and terraform apply to import

Query File Structure

Query files use .tfquery.hcl extension and support:

  • provider blocks for authentication
  • list blocks for resource discovery
  • variable and locals blocks for parameterization
# discovery.tfquery.hcl
provider "aws" {
  region = "us-west-2"
}

list "aws_instance" "all" {
  provider = aws
}

List Block Syntax

list "<list_type>" "<symbolic_name>" {
  provider = <provider_reference>  # Required

  # Optional: filter configuration (provider-specific)
  # The `config` block schema is provider-specific. Discover available options using `terraform providers schema -json | jq '.provider_schemas."registry.terraform.io/hashicorp/<provider>".list_resource_schemas."<resource_type>"'`

  config {
    filter {
      name   = "<filter_name>"
      values = ["<value1>", "<value2>"]
    }
    region = "<region>"  # AWS-specific
  }
  # Optional: limit results
  limit = 100
}

Supported List Resources

Provider support for list resources varies by version. Always check what's available for your specific provider version using the discovery script.

Query Examples

Basic Discovery

# Find all EC2 instances in configured region
list "aws_instance" "all" {
  provider = aws
}

Filtered Discovery

# Find instances by tag
list "aws_instance" "production" {
  provider = aws

  config {
    filter {
      name   = "tag:Environment"
      values = ["production"]
    }
  }
}

# Find instances by type
list "aws_instance" "large" {
  provider = aws

  config {
    filter {
      name   = "instance-type"
      values = ["t3.large", "t3.xlarge"]
    }
  }
}

Multi-Region Discovery

provider "aws" {
  region = "us-west-2"
}

locals {
  regions = ["us-west-2", "us-east-1", "eu-west-1"]
}

list "aws_instance" "all_regions" {
  for_each = toset(local.regions)
  provider = aws

  config {
    region = each.value
  }
}

Parameterized Queries

variable "target_environment" {
  type    = string
  default = "staging"
}

list "aws_instance" "by_env" {
  provider = aws

  config {
    filter {
      name   = "tag:Environment"
      values = [var.target_environment]
    }
  }
}

Running Queries

# Execute queries and display results
terraform query

# Generate configuration file
terraform query -generate-config-out=imported.tf

# Pass variables
terraform query -var='target_environment=production'

Query Output Format

list.aws_instance.all   account_id=123456789012,id=i-0abc123,region=us-west-2   web-server

Columns: <query_address> <identity_attributes> <name_tag>

Generated Configuration

The -generate-config-out flag creates:

# __generated__ by Terraform
resource "aws_instance" "all_0" {
  ami           = "ami-0c55b159cbfafe1f0"
  instance_type = "t2.micro"
  # ... all attributes
}

import {
  to       = aws_instance.all_0
  provider = aws
  identity = {
    account_id = "123456789012"
    id         = "i-0abc123"
    region     = "us-west-2"
  }
}

Post-Generation Cleanup

Generated configuration includes all attributes. Clean up by:

  1. Remove computed/read-only attributes
  2. Replace hardcoded values with variables
  3. Add proper resource naming
  4. Organize into appropriate files
# Before: generated
resource "aws_instance" "all_0" {
  ami                    = "ami-0c55b159cbfafe1f0"
  instance_type          = "t2.micro"
  arn                    = "arn:aws:ec2:..."  # Remove - computed
  id                     = "i-0abc123"        # Remove - computed
  # ... many more attributes
}

# After: cleaned
resource "aws_instance" "web_server" {
  ami           = var.ami_id
  instance_type = var.instance_type
  subnet_id     = var.subnet_id

  tags = {
    Name        = "web-server"
    Environment = var.environment
  }
}

Import by Identity

Generated imports use identity-based import (Terraform 1.12+):

import {
  to       = aws_instance.web
  provider = aws
  identity = {
    account_id = "123456789012"
    id         = "i-0abc123"
    region     = "us-west-2"
  }
}

Verifying Imported State

After running terraform apply to import resources, verify what actually landed in state. Prefer the documented, stable, and more token-efficient commands over reading the raw state file:

# Confirm resources are now managed (also confirms addresses)
terraform state list

# Inspect resolved attribute values for imported resources
terraform show -json | jq '.values.root_module.resources[] | {address, type, name}'

terraform show -json requires providers to be installed (terraform init), since it renders values against provider schemas. Fall back to the raw state (terraform state pull / terraform.tfstate) only when providers aren't available and init can't run, you need only coarse info (addresses, outputs, serial/lineage), or you must avoid executing Terraform. Avoid parsing the raw version-4 state format as a stable interface. Note: state contains sensitive values in plaintext in every format — never echo state contents into logs or output.

Best Practices

Query Design

  • Start broad, then add filters to narrow results
  • Use limit to prevent overwhelming output
  • Test queries before generating configuration

Configuration Management

  • Review all generated code before applying
  • Remove unnecessary default values
  • Use consistent naming conventions
  • Add proper variable abstraction

Troubleshooting

IssueSolution
"No list resources found"Check provider version supports list resources
Query returns emptyVerify region and filter values
Generated config has errorsRemove computed attributes, fix deprecated arguments
Import failsEnsure resource not already in state

Complete Example

# main.tf - Initialize provider
terraform {
  required_version = ">= 1.14"
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "~> 6.0"  # Always use latest version
    }
  }
}

# discovery.tfquery.hcl - Define queries
provider "aws" {
  region = "us-west-2"
}

list "aws_instance" "team_instances" {
  provider = aws

  config {
    filter {
      name   = "tag:Owner"
      values = ["platform"]
    }
    filter {
      name   = "instance-state-name"
      values = ["running"]
    }
  }

  limit = 50
}
# Execute workflow
terraform init
terraform query
terraform query -generate-config-out=generated.tf
# Review and clean generated.tf
terraform plan
terraform apply

Más skills de hashicorp

provider-actions
hashicorp
Implementar acciones de proveedor de Terraform utilizando el Plugin Framework. Usar al desarrollar operaciones imperativas que se ejecutan en eventos de ciclo de vida (antes/después…
official
new-terraform-provider
hashicorp
Usa esto al crear la estructura de un nuevo proveedor de Terraform con el Plugin Framework: diseño del espacio de trabajo, configuración del módulo go, servidor del proveedor main.go y un provider.go…
official
terraform-test
hashicorp
Guía completa para escribir y ejecutar pruebas de Terraform. Úsala al crear archivos de prueba (.tftest.hcl), escribir escenarios de prueba con bloques run, validar…
official
terraform-test
hashicorp
Guía completa para escribir y ejecutar pruebas de Terraform con aserciones, simulación y validación de módulos. Escribe archivos de prueba usando la sintaxis .tftest.hcl con bloques run que se ejecutan en modo plan o apply, soportando ejecución secuencial y paralela con aislamiento de estado opcional. Afirma condiciones sobre atributos de recursos, salidas y fuentes de datos; usa expect_failures para validar que las entradas inválidas sean rechazadas correctamente. Simula proveedores (Terraform 1.7.0+) para simular el comportamiento de la infraestructura sin...
official
provider-actions
hashicorp
Implementa acciones imperativas del proveedor de Terraform en eventos del ciclo de vida de recursos utilizando el Plugin Framework. Soporta disparadores de ciclo de vida antes/después de crear y antes/después de actualizar (los eventos de destrucción no están disponibles en Terraform 1.14.0). Requiere una definición de esquema adecuada con tipos de framework correctos, ElementType para colecciones y validadores para la validación de entrada. Incluye informes de progreso, gestión de tiempos de espera y manejo integral de errores para operaciones de larga duración. Implementa polling y...
official
aws-ami-builder
hashicorp
Construye imágenes personalizadas de Amazon Machine con el builder amazon-ebs de Packer. Automatiza la creación de AMIs a partir de AMIs fuente usando plantillas HCL con provisionadores para personalización (scripts shell, cargas de archivos, gestión de configuración). Soporta distribución multi-región de AMIs mediante ami_regions y filtrado flexible de AMIs fuente por nombre, propietario y tipo de virtualización. Autentica mediante variables de entorno, archivo de credenciales de AWS o perfiles de instancia IAM; incluye comandos de validación y construcción para la plantilla...
official
new-terraform-provider
hashicorp
Crea un nuevo proveedor de Terraform utilizando el Plugin Framework. Genera un nuevo espacio de trabajo de módulo Go con la convención de nomenclatura estándar "terraform-provider-" e inicializa las dependencias requeridas. Proporciona un archivo main.go de plantilla siguiendo los patrones del Plugin Framework de HashiCorp, con marcadores TODO para personalización. Valida la configuración ejecutando comandos de compilación y prueba para asegurar que el proveedor compile y pase las verificaciones iniciales. Gestiona el espacio de trabajo confirmando la intención antes de crear uno nuevo...
official
azure-verified-modules
hashicorp
Requisitos de certificación y mejores prácticas para módulos de Terraform en Azure que buscan cumplimiento con AVM. Aplica restricciones de versión del proveedor (azurerm >= 4.0, < 5.0; azapi >= 2.0, < 3.0) y prohíbe referencias a módulos basados en git, favoreciendo fuentes fijas del registro de Terraform. Exige el uso de snake_case en minúsculas para todos los identificadores, tipos de variables precisos, atributos de salida discretos mediante el patrón de capa anticorrupción, y locales ordenados alfabéticamente. Requiere variables de activación de características para nuevos recursos agregados...
official