-
-
Notifications
You must be signed in to change notification settings - Fork 52
feat: Add comprehensive Ombi support as request management service #1893
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
base: main
Are you sure you want to change the base?
Conversation
Co-authored-by: benscobie <[email protected]>
Co-authored-by: benscobie <[email protected]>
Co-authored-by: benscobie <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is an okay start but I left out some important details. As well as adding Ombi as a service, we should also add it to the rules engine (start from server\src\modules\rules\constants\rules.constants.ts). You can look at the Overseerr and Jellyseerr implementation for an idea of the type of fields people like to use rules on. You can use the Ombi OpenAPI spec to cross reference.
Co-authored-by: benscobie <[email protected]>
Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details. |
Co-authored-by: benscobie <[email protected]>
I've added Ombi to the rules engine as requested. The implementation includes:
The rules engine now supports Ombi with the same field types that users expect from Overseerr/Jellyseerr implementations. Implemented in commit 213a258. |
Co-authored-by: benscobie <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple more changes please
Co-authored-by: benscobie <[email protected]>
This PR adds complete Ombi integration to Maintainerr, allowing users to configure and use Ombi as a request management service alongside or instead of Overseerr/Jellyseerr.
Overview
The implementation follows the exact same patterns as existing Overseerr and Jellyseerr integrations to ensure consistency and maintainability across the codebase.
Changes Made
Backend (Server)
Database & Settings:
ombi_url
andombi_api_key
fields to settings entity and DTOtestOmbi()
in settings serviceGET /api/settings/test/ombi
API Integration:
ombi-api
module with service, controller, and helper classesNew API Endpoints:
GET /api/ombi/movie/requests
- Get movie requests from OmbiGET /api/ombi/tv/requests
- Get TV requests from OmbiGET /api/ombi/users
- Get users from OmbiDELETE /api/ombi/request/movie/{id}
- Delete movie requestDELETE /api/ombi/request/tv/{id}
- Delete TV requestDELETE /api/ombi/media/movie/tmdb/{id}
- Remove movie by TMDB IDDELETE /api/ombi/media/tv/tmdb/{id}
- Remove TV by TMDB IDFrontend (UI)
Settings Integration:
/settings/ombi
following Overseerr/Jellyseerr patternsombi_url
andombi_api_key
fieldsQuality Assurance
Usage
Users can now:
The integration supports all standard Ombi API operations including request retrieval, deletion, and user management, making it a full-featured alternative to Overseerr/Jellyseerr.
Fixes #1891.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.