Replies: 1 comment
-
|
FWIW in component-registry we had a base tag model on most entities because of this kind of uncontained/unknown set of 'categorize' requirements ... the problem though was knowing when a tag/label is just tactical metadata or grows up into its own full blown entity - at scale a generic tagging/labelling mechanism could become problematic (eg. search, sort) ... also doing tagging/labelling in graph we have open ended tagging/labeling mechanisms though that does not really help normal entities (or does it ?) ;) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Maybe it's too early, however I think we should consider the use of labels for inbound documents (SBOMs, maybe CSAF, …).
For SBOMs we have the idea of grouping them by product (#190). However, we might also want to categorize SBOMs in a different way (by CI job, by installed cluster, by product, …).
Labels seem to have a good way to deal with this problem.
Beta Was this translation helpful? Give feedback.
All reactions