use batch update instead of update incidents one by one; add progress… #82
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
… bay; retry smaller batch when batch fails
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.
… bay; retry smaller batch when batch fails
Link back to Jira ticket:
Description
From pdpyras >= 2.1.0 the Official Pager Duty update API can do batch update
Current one by one update takes too long.
There is no progress bar and good to have one.
Implementation
include package tqdm for simple progress bar
Hitting new api endpoint https://api.pagerduty.com/incidents for batch update
Auto re-try smaller batch size when a single batch fails
Steps to test changes
Documentation
No additional documentation needed.
Links to any documentation to be updated: