Sonarr: Link specific indexers to specific clients

[Londonlad95]

Hi,

Due to being a member of a private site it would be nice to be able to link specific indexers to specific clients so that I can use a proxy on the public client and no proxy on the private site client. Is this something which may be on the cards?

[hbh7]

+1 That would be fantastic. Considering setting up a second instance of Sonarr atm but I don't exactly want to as it's not ideal obviously.

[Xaelias]

Any chance this could be added to the roadmap?
It would be really nice to be able to send specific trackers to dedicated clients/instances with specific configs for these trackers.

[jpaige5408]

apologies for the dupe. but anyway, another +1 here

[samip5]

What would this actually require?

Re-write the decision making logic?

Which route is the best suitable, as in linking indexers to a specifc download client and then just having a default for everything else that's not linked?

[Thirrian]

I'd say tags is the obvious route to go.
Edit: to clarify, exactly as they work for profiles and connections. No tag = default.

[samip5]

I'd say tags is the obvious route to go.

If you mean the already existing tags, I don't know if I agree with you.
I would like some input from the actual Sonarr devs.

[markus101]

Not tags, those link to series.

I think @Taloth and I landed on an indexer would have a specific download client linked to it, similar to release profiles being linked to either a specific indexer or none (which behaves like all).

[Taloth]

yup, giving tags multiple meanings would become confusing fast.
I think I prefer this feature to stay limited to either one or all download clients per indexer, so no multi select.
Some notes for implementation:

• New nullable(default 0) integer column in database, not part of the setting json
• If the download client gets removed, Indexers associated with it must be disabled and changed to All

[samip5]

yup, giving tags multiple meanings would become confusing fast.
I think I prefer this feature to stay limited to either one or all download clients per indexer, so no multi select.
Some notes for implementation:

• New nullable integer column in database, not part of the setting json
• If the download client gets removed, Indexers associated with it must be disabled and changed to All

Could you elaborate more on the "no multi select"? What do you actually mean by that?

[Taloth]

meaning you can only restrict an indexer to one download client, not two out of three.

[BelgianMonster]

+1

Could definitely use this for separating public/private indexers

[samip5]

@Taloth "New nullable(default 0) integer column in database, not part of the setting json", settings json probably refers to the IConfigService?

[markus101]

No, that’s for app wide settings. Taloth means a new column in the download client or indexer table for that value, similar to priority for those is stored.

[samip5]

Ah, now I got the point, thanks. :)

[delbonis]

This would also be a very useful feature to me!

I'd be willing go contribute to a bounty if there was anything for that. 👍

[jonnes86]

I would love this; this would be immensely useful. I'd also be willing to contribute to a bounty.