Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: tf plan suggests changes in grafana_contact_point in every run after apply #1525

Closed
evertonspader-tomtom opened this issue Apr 30, 2024 · 2 comments

Comments

@evertonspader-tomtom
Copy link

evertonspader-tomtom commented Apr 30, 2024

Terraform Version

v1.8.0

Terraform Grafana Provider Version

v2.18.0

Grafana Version

No response

Affected Resource(s)

  • grafana_contact_point

Terraform Configuration Files

resource "grafana_contact_point" "pd_alert" {
  name = "Team - PD"
  pagerduty {
    integration_key = var.pd_key
    settings = {
       # ...
    }
  }
}

Expected Behavior

No changes in tf plan output after resources have been provisioned

Actual Behavior

In every plan run, all grafana_contact_point resources are set to have changes be applied:

# grafana_contact_point.pd_alert will be updated in-place
  ~ resource "grafana_contact_point" "pd_alert" {
        id                 = "Team - PD"
        name               = "Team - PD"
        # (2 unchanged attributes hidden)

      - pagerduty {
          # At least one attribute in this block is (or was) sensitive,
          # so its contents will not be displayed.
        }
      + pagerduty {
          # At least one attribute in this block is (or was) sensitive,
          # so its contents will not be displayed.
        }
    }

Steps to Reproduce

terraform plan
terraform apply -auto-approve

Then after resources are provisioned, re-run the commands

Important Factoids

No response

References

No response

@evertonspader-tomtom evertonspader-tomtom changed the title [Bug]: [Bug]: tf plan suggests changes in grafana_contact_point in every run after apply Apr 30, 2024
@julienduchesne
Copy link
Member

Is this on Grafana Cloud and is this still happening? I've tried to reproduce it on Grafana 10 and 11 (Cloud) and I'm unable to do so

@julienduchesne
Copy link
Member

Closing because I'm unable to reproduce, and this may be resolved with the new major version. I'd recommend you try that one. Feel free to re-open if this is still happening!

@julienduchesne julienduchesne closed this as not planned Won't fix, can't repro, duplicate, stale May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants