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

Resource newrelic_synthetics_script_monitor: Unable to Detect Differences in locations_public #2768

Closed
htnosm opened this issue Nov 1, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@htnosm
Copy link

htnosm commented Nov 1, 2024

Hi there,

In the newrelic_synthetics_script_monitor resource, it seems that the value for locations_public is not being retrieved.

While creating and updating resources via Terraform works without any issues, any manual updates to the locations_public value from the Web UI do not reflect in Terraform, and therefore, no differences are outputted.

Additionally, when using the generate-config-out option with the import command, the locations_public is outputted as null. This leads me to believe that there is a bug preventing the actual value of locations_public from being retrieved.

Terraform Version

  • v1.9.8
  • newrelic v3.51.0

Affected Resource(s)

  • newrelic_synthetics_script_monitor
  • newrelic_synthetics_* ?

Terraform Configuration

I checked with SCRIPT_API.

resource "newrelic_synthetics_script_monitor" "monitor" {
  status               = "ENABLED"
  name                 = "script_monitor"
  type                 = "SCRIPT_API"
  locations_public     = ["AP_SOUTH_1", "AP_EAST_1"]
  period               = "EVERY_6_HOURS"

  script               = "console.log('it works!')"

  script_language      = "JAVASCRIPT"
  runtime_type         = "NODE_API"
  runtime_type_version = "16.10"

  tag {
    key    = "some_key"
    values = ["some_value"]
  }
}

Actual Behavior

Differences in locations_public are not detected.

Expected Behavior

The locations_public value should be retrieved and any differences should be outputted.

Steps to Reproduce

  1. Create or update a newrelic_synthetics_script_monitor resource via Terraform.
  2. Manually update locations_public in the Web UI.
  3. Run terraform plan and observe that no differences in locations_public are detected.
@vagrawal-newrelic vagrawal-newrelic added the bug Something isn't working label Nov 4, 2024
@pranav-new-relic pranav-new-relic changed the title Unable to Detect Differences in locations_public for newrelic_synthetics_script_monitor Resource newrelic_synthetics_script_monitor: Unable to Detect Differences in locations_public Nov 5, 2024
@pranav-new-relic
Copy link
Member

Hi @htnosm, thank you for reporting this issue - we shall take a look soon, based on our current priority queue.
cc @vinay-newrelic

@pranav-new-relic
Copy link
Member

@htnosm a fix to this issue was made and released with v3.53.0 of the New Relic Terraform Provider. Please test this at your convenience. Thank you for reporting this again :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants