Skip to content

feat: add parlay as tool during enrichments#94

Draft
mcombuechen wants to merge 1 commit intomainfrom
82-tool-entry
Draft

feat: add parlay as tool during enrichments#94
mcombuechen wants to merge 1 commit intomainfrom
82-tool-entry

Conversation

@mcombuechen
Copy link
Collaborator

Adds parlay as a tool used during SBOM creation when running

  • ecosystems enrich
  • scorecard enrich
  • snyk enrich

This behaviour is opt-out through the --omit-watermark flag.

Closes #82.

@mcombuechen mcombuechen force-pushed the 82-tool-entry branch 2 times, most recently from 8a56cd7 to 796528b Compare December 12, 2024 10:27
// Handle possibly existing, legacy "Tools" entry
if bom.Metadata.Tools.Tools != nil {
//nolint:staticcheck // Intentionally using a deprecated type in this case.
*bom.Metadata.Tools.Tools = append(*bom.Metadata.Tools.Tools, cdx.Tool{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we check if name (and version for the components) already exists? I assume we don't want to clutter the tools array with parlay multiple times if the users runs different enrichers sequentially

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Parlay should add itself as a tool in the SBOM

2 participants