You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The aggregation delay was set before to 120, and when I changed it to 0 nothing was changed in terraform when running terraform plan & apply
Expected Behavior
The value of the aggregation delay params needs to be changed to 0 from 120, the weird behavior that I was able to detect is that the value of the aggregation delay is updated for whatever value other than 0 when the current value is 120, for example, if I change it to 300 from 120 it will be updated to 5 minutes in the state file and in the UI, then once it is 300 I can update it to 0 and it will be reflected in the state file, the only blocker here is when the value is 120 it cannot be updated to 0.
Steps to Reproduce
terraform apply
The text was updated successfully, but these errors were encountered:
walid-farhani
changed the title
newrelic_nrql_alert_condition aggregation delay value reset to default
[bug] newrelic_nrql_alert_condition aggregation delay value reset to default
Nov 28, 2023
Terraform Version
Terraform v1.5.5
on darwin_arm64
Affected Resource(s)
newrelic_nrql_alert_condition
Terraform Configuration
Actual Behavior
The aggregation delay was set before to 120, and when I changed it to 0 nothing was changed in terraform when running terraform plan & apply
Expected Behavior
The value of the aggregation delay params needs to be changed to 0 from 120, the weird behavior that I was able to detect is that the value of the aggregation delay is updated for whatever value other than 0 when the current value is 120, for example, if I change it to 300 from 120 it will be updated to 5 minutes in the state file and in the UI, then once it is 300 I can update it to 0 and it will be reflected in the state file, the only blocker here is when the value is 120 it cannot be updated to 0.
Steps to Reproduce
terraform apply
The text was updated successfully, but these errors were encountered: