Address: Schedules can't be deleted when they have open incidents #602
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.
Address: #567
This update doesn't provide an strict solution to the issue, because unfortunately the Provider shouldn't be closing incidents on its own in an arbitrary fashion. However what it does provide is an error message containing a list with the urls pointing to each incident which needs to be resolved in order of retrying the Schedule destruction after the incidents are been resolved.
Example of error message expected...
Test cases introduced...
Depends on: heimweh/go-pagerduty#109