-
The user connects with nexus1 and requests the package (e.g., eclipse).
-
The remote url of nexus1 becomes nexus2, the remote url of nexus2 becomes nexus 3, and the remote url of nexus3 becomes the external repository (ex. https://repo1.maven.com).
-
Nexus1 received a package or library request from the user is delivered to Nexus2 through remote url.
-
Nexus2 sends a request to nexus3, and because of the configuration of nexus repository, nexus 1,2,3 all have the package or library you requested saved through nexus3.
5.However, nexus1 should not store the requested package or library because the nexus I am trying to configure may have a package or library with a license or vulnerability due to internal policy. (must be stored only on nexus2 and nexus3)
As a result, the user makes a package or library request through nexus1, but the data requested by nexus1 should not be accepted directly.
This is because we need to push to nexus1 after checking if there is no problem using the package or library requested by the user in nexus2.
Is there any setting or method for this configuration?