Prowlarr API Key and tag support

[onedr0p]

Hi 👋🏼

It would be awesome to supply a Prowlarr API key and a tag that can be used to auto-discover the indexers.

So instead of having a config like this:

module.exports = {
  qbittorrentUrl: "http://localhost",
  torznab: [
    "http://prowlarr.default.svc.cluster.local/1/api?apikey={{ .PROWLARR__API_KEY }}",
    "http://prowlarr.default.svc.cluster.local/2/api?apikey={{ .PROWLARR__API_KEY }}",
    "http://prowlarr.default.svc.cluster.local/6/api?apikey={{ .PROWLARR__API_KEY }}",
    "http://prowlarr.default.svc.cluster.local/8/api?apikey={{ .PROWLARR__API_KEY }}",
    "http://prowlarr.default.svc.cluster.local/11/api?apikey={{ .PROWLARR__API_KEY }}",
    "http://prowlarr.default.svc.cluster.local/20/api?apikey={{ .PROWLARR__API_KEY }}",
    "http://prowlarr.default.svc.cluster.local/21/api?apikey={{ .PROWLARR__API_KEY }}",
    "http://prowlarr.default.svc.cluster.local/26/api?apikey={{ .PROWLARR__API_KEY }}",
    "http://prowlarr.default.svc.cluster.local/38/api?apikey={{ .PROWLARR__API_KEY }}",
    "http://prowlarr.default.svc.cluster.local/39/api?apikey={{ .PROWLARR__API_KEY }}",
    "http://prowlarr.default.svc.cluster.local/40/api?apikey={{ .PROWLARR__API_KEY }}",
    "http://prowlarr.default.svc.cluster.local/42/api?apikey={{ .PROWLARR__API_KEY }}",
    "http://prowlarr.default.svc.cluster.local/44/api?apikey={{ .PROWLARR__API_KEY }}",
    "http://prowlarr.default.svc.cluster.local/45/api?apikey={{ .PROWLARR__API_KEY }}",
    "http://prowlarr.default.svc.cluster.local/46/api?apikey={{ .PROWLARR__API_KEY }}",
    "http://prowlarr.default.svc.cluster.local/47/api?apikey={{ .PROWLARR__API_KEY }}",
  ],
  // ...
};

It could be done like this where prowlarr is the source of truth for indexers that cross-seed will search...

module.exports = {
  qbittorrentUrl: "http://localhost",
  prowlarrUrl: "http://prowlarr.default.svc.cluster.local",
  prowlarrApiKey: "{{ .PROWLARR__API_KEY }}",
  prowlarrTag: "cross-seed",
  // ...
};

Cross seed could then look up what indexers have the cross-seed tag in Prowlarr and use them in their searches instead of defining which ones to use in the cross-seed config file.

[mouzzampk2014]

Yes this is one slick approach 👌

[samip5]

Is the idea that you would want cross-seed to send a bulk request to those indexers that correspond to the tag in Prowlarr?

[onedr0p]

Yeah, that's that idea. It would basically be having cross-seed auto-populate the torznab list based on API calls to prowlarr and looking up which indexers have the tag defined in the config.

[mmgoodnow]

we used to have this with jackett, and I removed it when I added Prowlarr support because torznab is an open spec that anyone can implement, and it could support both jackett and Prowlarr at the same time.

I'm probably not going to do this any time soon, but I do recognize the convenience it would provide. Eventually I'm hoping to have endpoints Prowlarr can use in the same way it keeps Sonarr/Radarr's indexers up to date, but that's part of a larger rewrite.

[onedr0p]

Sounds good, it would be neat to see some tighter prowlarr integration since it also can report back health / status of indexers (and time disabled until) instead of cross-seed having to have store and do the logic. It's been a couple years since I've used jackett but I realize there are some people who do prefer jackett more however I don't know why at this point, maybe just stubbornness to migrate, or some niche tracker that prowlarr doesn't support? lol.

[xiNeRoar]

this will be a lot more convenient for people who have over 100+ indexers, really painful to maintain and keep all the indexers up to date with the current method..especially with no names and tags available, just bunch of ids. it is nearly impossible to maintain it :'(