How to configure routing in Nexus OSS 3

Question

Sonatype Nexus 2 has “routing” capabilities, so I can configure my requests for internal artifacts only to be served by some (internal) repositories.

I have a version of Nexus 3, but I don’t see the opportunity to implement this feature. There is something called “content selectors” that may be a new mechanism, but there is absolutely no documentation, so I cannot use it. This is a pretty important security requirement.

Am I missing something? How to send requests in Nexus 3?

Answer 1

, nexus, ​​ Nexus 3. , nexus 2 , .

Answer 2

; , " Nexus 2" " Nexus 3".

, Sonatype Nexus 2 "" " " Nexus 3 JEXL . 4 Nexus Repository Manager 3.1.

→ .

JEXL , . , com/mycompany maven2:

format == "maven2" && path =^ "com/mycompany/"

, "Preview" buttun.

, Nexus 2.

→ → →

, " ", (, ),

read,browse

.

→ → , .

, , .

Answer 3

Nexus 3.17 has been released. This is the first version to support routing rules. They do not work the same as in Nexus 2.X, but they meet the same needs. Things are now focused on the rules, not the repo. I found that the Nexus 3 approach is easier to understand.

This documentation page shows the new routing rules.