grafana_organization resource is not working as expected after addition of grafana admin user in admins list

[Shindek77]

Terraform Version

Terraform v1.8.0
on darwin_arm64

Terraform Configuration Files

resource "grafana_organization" "organization" {
  name         = "Test Organization"
  admin_user   = "admin"
  create_users = true
  admins = [
    "admin@localhost"
  ]
}

Debug Output

na

Expected Behavior

on first terraform apply it should show

 + resource "grafana_organization" "organization" {
      + admins               = [
          + "admin@localhost",
        ]
        id                   = "7"
        name                 = "Test Organization"
    }

Plan: 1 to add, 0 to change, 0 to destroy.

But if we do second terraform apply then it should say
`No Changes`

Actual Behavior

but on second terraform apply it shows as follows:

   # resource.organization["grafana_org_config-8"].grafana_organization.organization will be updated in place
  ~ resource "grafana_organization" "organization" {
      ~ admins               = [
          + "admin@localhost"
        ]
        id                   = "7"
        name                 = "Test Organization"
        # (2 unchanged attributes hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

Why its showing one to change as its already added as admin user in tfstate also and on Grafana UI also as we verified.

Steps to Reproduce

1. Create new Test org on Grafana with admin@localhost user added in admins list
2. Use Grafana provider with grafana_orgnization resource and do terraform plan and apply 2 3 times

Additional Context

No response

References

No response

Generative AI / LLM assisted development?

No response

[liamcervante]

Hi @Shindek77, have you checked in with the grafana provider directly about this issue? I think this is more likely to be something specific to the Grafana provider rather than anything within Terraform Core.

If so, can you confirm if the admin user is present in the state file after the first apply, and can you check the output of running terraform plan -refresh-only? This would help us narrow down the problem to a specific part of the Terraform lifecycle. Thanks!