Fix Radarr upgrade processing to respect quality profile upgrade allowed setting #762
Conversation
This file contains hidden or 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
…wed setting - Fetch quality profiles at start of upgrade processing - Filter out movies without upgrade allowed quality profiles - Log profile name when skipping movies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
While working on another change, I noticed that the integration with Radarr was kicking off searches for movies that were part of a quality profile that didn't allow upgrades. This change adjusts the logic so that it keeps track of which profiles actually permit upgrades.
To test, I'm running this branch and I can see it's skipping non-upgradable movies and such.