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
-/+ module.alerting.newrelic_alert_channel.alerting
configuration.%:"0"=>"3" (forces new resource)
configuration.service_key:"<sensitive>"=>"<sensitive>" (forces new resource)
configuration.service_name:"<sensitive>"=>"<sensitive>" (forces new resource)
configuration.subdomain:"<sensitive>"=>"<sensitive>" (forces new resource)
name:"alerting-pagerduty-production"=>"alerting-pagerduty-production"
type:"pagerduty"=>"pagerduty"-/+ module.alerting.newrelic_alert_policy_channel.alerting
channel_id:"223790"=>"0" (forces new resource)
policy_id:"57733"=>"57733"
It seems like the configuration hash might not be being sent from the newrelic API, therefore the newrelic provider thinks it has to re-add it every time.
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 9, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Terraform Version
0.9.2
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
No changes should be detected
Actual Behavior
It seems like the configuration hash might not be being sent from the newrelic API, therefore the newrelic provider thinks it has to re-add it every time.
The text was updated successfully, but these errors were encountered: