Dynamic Block causing Unexpected Block: Blocks of type "dynamic" are not expected here.

[michaelrichards-cosmo]

Extension Version

v2.34.2

VS Code Version

Version: 1.96.2 (user setup)
Commit: fabdb6a30b49f79a7aba0f2ad9df9b399473380f
Date: 2024-12-19T10:22:47.216Z
Electron: 32.2.6
ElectronBuildId: 10629634
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.22631

Operating System

Windows 11 Enterprise version 23H2

Terraform Version

Terraform v1.10.3 on Windows_386

Steps to Reproduce

Main.TF

resource "azurerm_dev_center" "adc" {
name = lower("adc-${var.environment}-${var.solution_name}-${var.location}-${var.instance_number}")
resource_group_name = var.resource_group_name
location = var.location
}

#Dynamic creation of projects
dynamic "project" {
for_each = var.projects
content {
resource "azurerm_dev_center_project" "example" {
name = project.value.name
dev_center_id = azurerm_dev_center.example.id
description = project.value.description
}
}
}

Variables TF:

variable "projects" {
description = "List of projects"
type = list(object({
name = string
description = string
}))
}

Expected Behavior

This is valid syntax. I wouldn't expect the dynamic block to be throwing the error

Actual Behavior

In the Main.TF, IntelliSense indicating: Unexpected Block: Blocks of type "dynamic" are not expected here.

Terraform Configuration

No response

Project Structure

No response

Gist

No response

Anything Else?

No response

Workarounds

No response

References

Similar to 1594 and 1877

Help Wanted

• I'm interested in contributing a fix myself

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

[dbanck]

Hi @michaelrichards-cosmo,

I've never seen a dynamic block at the top level of a Terraform configuration and terraform validate also reports an error

Are you using something else than Terraform to transform this configuration?

[michaelrichards-cosmo]

Hi @dbanck ,

Maybe I'm misunderstanding. Below is another example where we have a dynamic nsg for a subnet that matches the same format and level. This works (validates and deploys successfully). I don't see the difference between what I've got for the adc and the subnet module below.

resource "azurerm_subnet" "snet" {
  name                              = lower("snet-${var.environment}-${var.solution}-${var.location}-${var.instance_number}")
  resource_group_name               = var.vnet_resource_group_name
  virtual_network_name              = var.virtual_network_name
  address_prefixes                  = var.address_prefixes
  private_endpoint_network_policies = var.private_endpoint_network_policies
  service_endpoints                 = ["Microsoft.Storage", "Microsoft.KeyVault", "Microsoft.Web", "Microsoft.Sql"]


}


resource "azurerm_network_security_group" "nsg" {
  name                = lower("nsg-${var.environment}-${var.solution}-${var.location}-${var.instance_number}")
  location            = var.location
  resource_group_name = var.vnet_resource_group_name
  tags                = var.tags


  security_rule {
    name                       = "Azure_DevOps"
    priority                   = 111
    direction                  = "Inbound"
    access                     = "Allow"
    protocol                   = "*"
    source_port_range          = "*"
    destination_port_range     = "8080"
    source_address_prefix      = "AzureDevOps"
    destination_address_prefix = "VirtualNetwork"
  }

  #Dynamic Block
  dynamic "security_rule" {
    for_each = var.security_rules
    content {
      name                       = security_rule.value.name
      priority                   = security_rule.value.priority
      direction                  = security_rule.value.direction
      access                     = security_rule.value.access
      protocol                   = security_rule.value.protocol
      source_port_ranges         = security_rule.value.source_port_ranges
      destination_port_ranges    = security_rule.value.destination_port_ranges
      source_address_prefix      = security_rule.value.source_address_prefix
      destination_address_prefix = security_rule.value.destination_address_prefix
    }
  }

}

[dbanck]

The example in your initial post has a dynamic block at the top level of the file and not inside a resource block. Furthermore it has a resource block inside a content block.

resource "azurerm_dev_center" "adc" {
  name                = lower("adc-${var.environment}-${var.solution_name}-${var.location}-${var.instance_number}")
  resource_group_name = var.resource_group_name
  location            = var.location
}

#Dynamic creation of projects
dynamic "project" {
  for_each = var.projects
  content {
    resource "azurerm_dev_center_project" "example" {
      name          = project.value.name
      dev_center_id = azurerm_dev_center.example.id
      description   = project.value.description
    }
  }
}

Maybe something went wrong while copy pasting this initial example?

[mloskot]

I'm experiencing similar issue for my uses of dynamic with the helm_release resource:

resource "helm_release" "cert_manager" {
  name        = "cert-manager"
  namespace   = kubernetes_namespace_v1.cert_manager.metadata[0].name

  chart      = "cert-manager"
  repository = "https://charts.jetstack.io"
  version    = var.cert_manager.version

  dynamic "set" {
    for_each = merge(
      local.cert_manager_annotations_pod,
      local.cert_manager_annotations_service,
      local.cert_manager_annotations_serviceaccount
    )

    content {
      name  = set.key
      value = set.value
    }
  }

  values = [
    templatefile("${path.module}/templates/cert-manager/values.yaml.tftpl", { ... }
  ]

OS: Ubuntu 25.04
VS Code: 1.104.3
Terraform Extension: 2.37.2
Terraform: 1.33

Update

I've just tested it a bit more and noticed something peculiar:

• In .tf file in reusable module, my use of dynamic IS reported as not expected here
• In .tf file in root module, my use of dynamic IS NOT reported as not expected here

[jtackaberry]

I'm experiencing similar issue for my uses of dynamic with the helm_release resource:

@mloskot the helm provider changed from blocks to nested objects from provider v2 to v3. I think the problem is actually with https://github.com/hashicorp/terraform-ls (which this project uses) because I run into this same issue with neovim using terraform-ls, and my module is clearly defining a 2.x version constraint on the helm provider. I think terraform-ls isn't properly respecting the provider version defined in the project and is issuing diagnostics based on the latest provider version only, which is why we're seeing this.

[mloskot]

I think terraform-ls isn't properly respecting the provider version

@jtackaberry Good points! It looks like this issue may be related

• Many official providers have outdated schemas that are breaking changes terraform-ls#2001