Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Find a way to include original BOMs (or references to them) in notifications #646

Open
nscuro opened this issue Jun 29, 2023 · 1 comment
Labels
component/api-server domain/notifications enhancement New feature or request feature-gap Things that work in vanilla Dependency-Track but don't in Hyades p3 Nice-to-have features

Comments

@nscuro
Copy link
Member

nscuro commented Jun 29, 2023

Due to Kafka message size limitations, we had to exclude original BOM and VEX contents from notifications of the following groups:

  • BOM_CONSUMED
  • BOM_PROCESSED
  • VEX_CONSUMED
  • VEX_PROCESSED

We should provide an alternative that still allows notification consumers to get a hold of the original documents.

Note
This issue has significant overlap with #633.

@nscuro nscuro added enhancement New feature or request p3 Nice-to-have features domain/notifications component/api-server feature-gap Things that work in vanilla Dependency-Track but don't in Hyades labels Jun 29, 2023
@sahibamittal
Copy link
Collaborator

Can we just include Bom_Ref id in the notification content? and then user can use API endpoint to fetch Bom details using reference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/api-server domain/notifications enhancement New feature or request feature-gap Things that work in vanilla Dependency-Track but don't in Hyades p3 Nice-to-have features
Projects
None yet
Development

No branches or pull requests

2 participants