-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
Add support disabling sonarr or radarr #124
Comments
Yes this hasn't been added yet, I've been thinking about this, implementing this config would be the first step in a few other features as well:
It's not as simple as adding a config to disable the feature, because right now The best way to implement this would be to set:
to:
This will fail the compiler (in Scala this is what we want). Going one by one through all the compiler errors will ensure that we've correctly implemented this due to the strong type safety. |
I was going to open a separate issue (and still can if desired), but I think it makes sense to bring up here: I'm one of the people that would love to be able to push requests to multiple instances of radarr/sonarr. I have separate HD/4K/DV instances for each *arr. Right now, I'm:
If watchlistarr could push to multiple instances, it would basically eliminate all the unnecessary lead time in my set up. I decided to post on this issue because I think refactoring the config to use a list of radar/sonarr instances would solve both problems since you could just leave either list empty to disable it. |
Partially due #108, i'm not interested of allowing fulfilling sonarr requests at this time. but doesn't seem to be possible to disable sonarr integration, it can result just app startup failure if I fill bogus URL there: #120
perhaps:
enabled: true
option to config?The text was updated successfully, but these errors were encountered: