Our use case is to adjust how we auto-allow new versions of approved packages. Currently we utilize the API and the promotion capability. But we'd like to revisit using the Filter to do the same without having to maintain the separate process.

In years past we had tried, but it was noted that it is not recommended as it would cause performance degradation when ProGet does an index update.

While connector filters were never really designed to replace the "approved packages" workflow, we've seen many users do exactly that over the years, yielding hundreds of entries.

It's not exactly a use case we recommend, as one of the big benefits of the approved packages flow is to prevent "instinctively upgrading dependencies" yielding in regressions. But, if you're already effectively doing that through automation, then I suppose you already know the risks :)

From a performance standpoint, it shouldn't make a notable impact. Those have been optimized for quite some time now.

Thanks,
Alana