Repository navigation
Description
Problem
A request router plugin reads every setting of a request from the connection config an admin saved, or from a routing rule. The host can't tell that a setting such as a quality profile or root folder could be chosen per request. Only the admin can choose, and only in advance.
This comes up for anyone with one download server that serves several uses. The requester, or the admin approving the request, knows which profile or folder a title should get, but the plugin has no way to let them say so. It started from Silo-Community/silo-plugins-requests-seerr#10, which asks for Silo routes to choose the Seerr Radarr/Sonarr server, profile and folder. Solving it takes changes in this SDK, in silo-server and in the plugin.
Proposal
Add requester_options to RequestRouterDescriptor. Each entry names:
field: a select withdynamic_optionsin the plugin's admin form, which is the setting that can be chosen per request.media_typeandlabel: optional, for where the choice applies and how the host labels it.chooser_field: a static select in the same form where the admin says, per connection, who chooses. The values areadmin,requesterorapprover.
The host takes the choices from ListConfigOptions for the server the title would go to, checks the pick against them, and passes it as that key of RouterConnection.config. The plugin's RPCs don't change. Manifest validation requires field to be a select with dynamic_options, and chooser_field to be a static select that offers only those three values.
Compatibility
- An older host drops the unknown field and never offers the choice, so a plugin can declare options without raising its minimum host version.
- No existing field changes meaning.
- A Silo host that predates the field refuses a bare plugin binary that declares it, because it reads a binary's manifest strictly. On such a host the plugin has to be installed from an archive. This goes in
docs/compatibility.md.
Alternatives considered
- A boolean per option (
allow_requester_choice): it can't also express "the approving admin chooses" without another field. - A new RPC for per-request choices: it would change the plugin contract for something the host can do by overlaying config, as it already does for route overrides.
PRs
- Server feat(requests): let a requester or approving admin choose a request router plugin's settings silo-server#4040
- SDK feat(request-router): let a plugin leave connection settings to the r… #68
- Plugin feat(seerr): choose the quality profile and root folder per request Silo-Community/silo-plugins-requests-seerr#14
AI disclosure: Claude Code, claude-sonnet-5-5, fully AI-generated, human verified.
Activity