HashiTalks 2026 is the annual global community event for HashiCorp users and practitioners. Infrastructure teams discussed UUID v7 as a cross-tool correlation ID — the same UUID v7 used as a Terraform resource tag, a Vault request ID, and a Nomad job meta value links all infrastructure events for a single deployment in chronological order. See UUID in Terraform for implementation details.

Event details

ConferenceHashiTalks 2026
DateFebruary 19, 2026
LocationOnline (global)
FocusUUID v7 in Terraform, Vault, Consul, and Nomad infrastructure tooling

Key sessions

Terraform with UUID v7 correlation tags

# Generate UUID v7 via external data source
data "external" "deploy_id" {
  program = ["python3", "-c", <<-EOF
    import uuid, json, sys
    print(json.dumps({"id": str(uuid.uuid7())}))
  EOF
  ]
}

locals {
  deploy_id = data.external.deploy_id.result.id
}

# Tag all resources with UUID v7 deployment ID
resource "aws_instance" "web" {
  ami           = var.ami_id
  instance_type = "t3.micro"

  tags = {
    Name       = "web-${var.env}"
    DeployId   = local.deploy_id   # UUID v7 — encodes deploy time
    ManagedBy  = "terraform"
  }
}

resource "aws_db_instance" "postgres" {
  # ...
  tags = {
    DeployId = local.deploy_id   # Same UUID v7 ties DB and EC2 together
  }
}

See UUID in Terraform.

Vault dynamic secret request with UUID v7 correlation

# Generate UUID v7 correlation ID before secret request
CORRELATION_ID=$(python3 -c "import uuid; print(uuid.uuid7())")

# Request dynamic database credentials with correlation ID in metadata
vault write database/creds/my-role \
  -format=json \
  | jq --arg cid "$CORRELATION_ID" '. + {correlation_id: $cid}'

# Log the correlation ID alongside the lease
echo "Vault lease correlation: $CORRELATION_ID (created: $(date -u))"

Consul service registration with UUID v7 health check ID

{
  "service": {
    "id":   "web-018fbe3a-4c5d-7b12-8f3e-1a2b3c4d5e6f",
    "name": "web",
    "port": 8080,
    "checks": [
      {
        "id":       "check-018fbe3a-4c5d-7b12-8f3e-1a2b3c4d5e6f",
        "http":     "http://localhost:8080/health",
        "interval": "10s",
        "notes":    "UUID v7 check ID encodes registration time"
      }
    ]
  }
}

Nomad job with UUID v7 correlation meta

job "api-deploy" {
  datacenters = ["dc1"]
  type        = "service"

  meta {
    # UUID v7 generated at job submission — encodes submission time
    correlation_id = "018fbe3a-4c5d-7b12-8f3e-1a2b3c4d5e6f"
    deploy_env     = "production"
  }

  group "api" {
    task "server" {
      driver = "docker"
      config { image = "api:latest" }

      env {
        # Inject correlation ID into the running task
        CORRELATION_ID = "${NOMAD_META_correlation_id}"
      }
    }
  }
}

Conference takeaways

  1. Terraform — UUID v7 deploy tags link EC2, RDS, and S3 resources from the same apply run
  2. Vault — UUID v7 correlation IDs in audit logs encode request time without querying by timestamp
  3. Consul — UUID v7 service and check IDs make registration time visible in the service catalog
  4. Nomad — UUID v7 job meta correlation IDs propagate to all allocation logs
  5. Cross-tool correlation — one UUID v7 per deploy ties Terraform, Vault, Consul, and Nomad events together

Further reading

External references

Frequently asked questions

How do I generate UUID v7 in Terraform?

Terraform's random provider generates UUID v4 with resource "random_uuid". For UUID v7, use a null_resource with a local-exec provisioner running a script, or generate UUID v7 externally and pass it as a variable. Alternatively, use the external data source with a shell script: data "external" "uuid_v7" { program = ["sh", "-c", "echo '{\"id\":\"'$(python3 -c \"import uuid; print(uuid.uuid7())\")'\"}'"] }. See UUID in Terraform.

How does UUID v7 help with HashiCorp Vault lease correlation?

Vault generates its own lease IDs internally, but application-layer correlation IDs can be UUID v7 — included as metadata when requesting secrets. The UUID v7 timestamp lets operators identify which secrets were requested in a given time window during incident review, without querying the Vault audit log by time range separately. UUID v7's timestamp prefix makes the correlation ID self-describing.

How does UUID v7 improve Nomad job tracing?

Set a UUID v7 correlation ID in Nomad job meta: meta { correlation_id = "018fbe3a-..." }. This ID propagates to all allocations and appears in task logs. UUID v7's timestamp tells you exactly when the job was submitted — useful in postmortems where you need to correlate a Nomad allocation with a Kubernetes event or database row from the same time window.