mendRnvAutoDiscoverFilter - server-side or client-side filtering?

[holysoles]

I was initially testing out a POC of renovate with the CLI tool, but have moved to a renovate-ce helm installation as I begin to finalize the deployment.

I had been using this configuration for autodiscovery:

      autodiscover: true,
      autodiscoverNamespaces: ["PrimaryGroup/subgroup"],
      autodiscoverProjects: ["demo-project"],

I chose to use the autodiscoverNamespaces feature over autoDiscoverFilter because the documentation says the namespace filtering is done server-side:

You can use this option to autodiscover projects in specific namespaces (a.k.a. groups/organizations/workspaces). In contrast to autodiscoverFilter the filtering is done by the platform and therefore more efficient.

This seems to be also confirmed based on autodiscoverFilter using renovate's custom string match logic, which would imply its client-side filtering.

However, autodiscoverNamespaces/autodiscoverProjects doesn't seem to work with the helm installation (and possibly also the Docker image, I haven't used that). Reviewing the values file documentation, it says we must use the autodiscoverFilter, which should support my use case, but wouldn't it be incorrect to say autodiscoverFilter is server-side filtering?

  # Optional, a string of a comma separated values. (e.g. `org1/*, org2/test*, org2/test*`). Same behavior as Renovate cli 'autodiscoverFilter' feature
  # Warning: The Renovate CLI 'autodiscover' configuration option is disabled.
  # Repository filtering should solely rely on server-side filtering using 'mendRnvAutoDiscoverFilter'.
  mendRnvAutoDiscoverFilter:

If the values documentation is incorrect, I'm happy to open a PR, but I'm also curious why the more-efficient filtering option is not supported by the helm installation, as I haven't found an explanation for that.