Open vividly789 opened 2 months ago
Facing similar error when attempting to update pagerduty_escalation_policy
. Provider version (3.11.4) hasn't changed in a while, we've been using it successfully until today.
```hcl
Terraform will perform the following actions:
# module.pagerduty.pagerduty_escalation_policy.team_oncall_escalation_policy[0] will be updated in-place
! resource "pagerduty_escalation_policy" "team_oncall_escalation_policy" {
id = "
```hcl
module.pagerduty.pagerduty_escalation_policy.team_oncall_escalation_policy[0]: Modifying... [id=
@cjgajard, can we kindly prioritise this? :) Would love to help you guys test it or provide more feedback.
Terraform Version
Affected Resource(s)
Terraform Configuration Files
Stack trace from the
terraform-provider-pagerduty_v3.14.4
plugin:It looks like the provider is crashing here, while attempting to process the
name
attribute for thepagerduty_service
resource:d.Set("name", service.Name)
FWIW, it doesn't look from the Terraform plan like Terraform would have been trying to update the
name
attribute for the apply(checked the terraform plan for both failure one and successful one)Debug Output
Below is a link to snippet of the last HTTP request the provider made before the crash:
https://gist.github.com/vividly789/46b96d4e28ef562f1812ca60fcd341f7
Looking in the debug log, I think this could have been caused by a PagerDuty API issue! But its worth erroring out more gracefully if the API returns an error that the provider handle, without crashing.
Panic Output
panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0xd8 pc=0xe96f76]
Expected Behavior
Expect resource to be created during Terraform apply
Actual Behavior
I confirmed that terraform apply fails with the following message.
Steps to Reproduce
This appears to be an arbitrary error that only occurs sometimes when running terraform.