feat: Add support for Nexus v3 to NexusAnalyzer #5849
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes Issue #5319
Description of Change
Implement support for Nexus V3 REST API to search for artifact by SHA-1 hash in addition to the current Nexus V2 API support.
The NexusAnalyzer now attempts to use Nexus v2 API if the standard Nexus v2 API prefix (
service/local) is found in the Nexus Analyzer URL. Otherwise it will attempt to use the Nexus v3 API.Have test cases been added to cover the new functionality?
Existing test-case for NexusV2 has been cloned into a copy for V3, including the
@Ignoreof all testcases by default. Locally they have been used to test against private Nexus Repository OSS V2 and Nexus Repository OSS V3 instances to validate that both the Nexus V2 and Nexus V3 implementations are passing the tests.