Support for gracefully destroy pagerduty_schedule
#561
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… Policy deps error
stmcallister
approved these changes
Aug 25, 2022
There was a problem hiding this comment.
Great implementation for this issue! Nice work, @imjaroiswebdev!! 🌮 🎉 🍕
This was referenced Aug 25, 2022
|
when will this be released? |
Hi @nthienan This fix was made available in v2.6.1 of PagerDuty Terraform Provider. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addresses #337, #358 and #534
This change is aimed to solve the recurring issue when trying to destroy a
pagerduty_scheduleresource which ends with the following error log...Currently the
pagerduty_scheduledestroy implementation can't surpass the above mentioned error, because when a Schedule is being used by one or many Escalation Policies, it's needed to remove theschedule_referencetargets from the Escalation Policies, and only after that is completed a graceful delete operation can be executed on the Schedule. So, this change includes the API calls for following previously explained flow.Test Results...