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

Address: 403 Forbidden error when updating existing pagerduty_escalation_policy's target #846

Merged

Conversation

imjaroiswebdev
Copy link
Contributor

Closes #819

@imjaroiswebdev imjaroiswebdev requested a review from cjgajard April 5, 2024 17:20
@imjaroiswebdev imjaroiswebdev force-pushed the issue-819-403-querying-ep branch from 432ba9b to 711972f Compare April 5, 2024 17:30
@imjaroiswebdev imjaroiswebdev requested a review from cjgajard April 5, 2024 17:30
@imjaroiswebdev imjaroiswebdev merged commit 3e196bc into PagerDuty:master Apr 5, 2024
1 check passed
@langenoja
Copy link

langenoja commented Apr 8, 2024

Tried out the latest release (3.11.1) and am still having this issue unfortunately, still getting 403 Forbidden on the PUT request for updating the targets.

Terraform version: 1.5.1
Provider version: 3.11.1

}

if err == nil && escalationPolicyFirstAttempt == nil {
return setResourceEPProps(d, escalationPolicyFirstAttempt)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems wrong, should be if err == nil && escalationPolicyFirstAttempt != nil { instead of if err == nil && escalationPolicyFirstAttempt == nil { due to setResourceEPProps(d *schema.ResourceData, escalationPolicy *pagerduty.EscalationPolicy) function is not checking if escalationPolicy is nil.

@vorotech
Copy link

Same here. Fix didn't help. Still getting 403

vorotech added a commit to trustwallet/terraform-provider-pagerduty that referenced this pull request Apr 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

403 Forbidden error when updating existing pagerduty_escalation_policy's target
5 participants