group_by inheritance lost when policy nesting too deep

[georgivalentinov]

Terraform Version

1.9.4

Terraform Grafana Provider Version

3.18.2

Grafana Version

11.3.1

Affected Resource(s)

• grafana_notification_policy

Terraform Configuration Files

resource "grafana_notification_policy" "default" {
  contact_point = "main"
  group_by      = ["..."]

  policy {
    policy {
      policy {
        policy {
        }
      }
    }
  }
}

Expected Behavior

Resource to be accepted withour errors. The same policy structure, defined via Grafana's web UI, is accepted and valid.

Actual Behavior

Terraform's plan returns an error:

The argument "group_by" is required, but no definition was found.

Steps to Reproduce

1. terraform plan

Important Factoids

This is the structure that Grafana's export to Terraform/HCL produces as well. So passing a similar policy to Terraform yields the that error.

Explicitly/manually adding group_by in the deepest policy instance makes the resource valid and Terraform accepts it:

resource "grafana_notification_policy" "default" {
  contact_point = "main"
  group_by      = ["..."]

  policy {
    policy {
      policy {
        policy {
          group_by = ["..."]
        }
      }
    }
  }
}

Doing one level less nesting also seems to be valid:

resource "grafana_notification_policy" "default" {
  contact_point = "main"
  group_by      = ["..."]

  policy {
    policy {
      policy {
      }
    }
  }
}

References

No response

[JacobsonMT]

Hi @georgivalentinov, it looks like there is a max depth of 4 in the TF model for policies. There is definitely something to improve here, though it's no entire clear exactly what that should be right now:

• Improve documentation.
• Clearer error when trying to nest past 4.
• Grafana API likely exports to TF with >4 nested policies possible.
• Allow more than 4 nested policies.