You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there, managed to implement your plugin into our Nexus Repository server, but it does not seem to respect any routing rules.
Other proxies (such as PyPi-proxy) do respect the routing rules.
What are you trying to do?
Block specific providers/modules from being served through nexus repository.
I do this through Nexus Repository 3 with its native Routing Rule feature.
If I apply a blacklist with .*, I expect it to not pull in anything, as that is the behaviour with other proxies.
Instead, everything is pulled in regardless of any whitelist/blacklist rule.
What feature or behavior is this required for?
Provider/module filtering through routing rules.
How could we solve this issue? (Not knowing is okay!)
Not sure how the integration works, I am more of an infrastructure engineer than a software dev.
Hi there, managed to implement your plugin into our Nexus Repository server, but it does not seem to respect any routing rules.
Other proxies (such as PyPi-proxy) do respect the routing rules.
What are you trying to do?
Block specific providers/modules from being served through nexus repository.
I do this through Nexus Repository 3 with its native Routing Rule feature.
If I apply a blacklist with
.*
, I expect it to not pull in anything, as that is the behaviour with other proxies.Instead, everything is pulled in regardless of any whitelist/blacklist rule.
What feature or behavior is this required for?
Provider/module filtering through routing rules.
How could we solve this issue? (Not knowing is okay!)
Not sure how the integration works, I am more of an infrastructure engineer than a software dev.
Anything else?
Nothing for now.
Thanks in advance for your reply!
cc @DarthHater @bhamail
The text was updated successfully, but these errors were encountered: