Modified way sub projects are determined from activityData to componentType attribute.#162
Merged
nichollsdave merged 1 commit intoblackducksoftware:masterfrom Apr 20, 2021
Merged
Conversation
… 0.0.56 to ensure the correct request header to obtain componentType
This file contains hidden or 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
NOTE this requires pip blackduck 0.0.56 to ensure the correct request header to obtain componentType e.g. pip install blackduck==0.0.56
It seems the activityData could in some scenarios contain data for sub projects and this broke the previous way this script determined which components were sub projects. There is a componentType attribute that solves the issue as long as a specific request header is sent - this is a public API. See /api-doc/public.html#_listing_bom_components . Switched to using this but it does require the latest blackduck PyPi module.