You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: schemas/env/sbom.cue
+3-26Lines changed: 3 additions & 26 deletions
Original file line number
Diff line number
Diff line change
@@ -5,15 +5,6 @@ import (
5
5
)
6
6
7
7
8
-
// supported formats for sbom generators
9
-
10
-
// common fields for sbom generators, used internally
11
-
sbomCommon: {
12
-
name?: string
13
-
path: string
14
-
data: _
15
-
}
16
-
17
8
// generate the CUE representation
18
9
// is a: *dagger.File with format:[cue,json,yaml,toml] content
19
10
// data: any CUE value
@@ -27,23 +18,9 @@ sbomCommon: {
27
18
$kind: "#cuefigSBOM"
28
19
format: or(["cue", "json", "yaml", "toml"])
29
20
30
-
sbomCommon
21
+
name?: string
22
+
path: string
23
+
data: _
31
24
}
32
25
33
-
// generate the Dagger representation
34
-
// is a: *dagger.File with JSON content
35
-
// data: any *dagger.Object (env.Ref, i.e. #Things)
36
-
// hmmm, can we reverse this one?
37
-
// update, can't seem to get anything reasonable out of dagger for sbom, misleading function names / what they return, it's all internal ids to ephemeral object, not actual sbom material
38
-
// #DaggerSBOM: Ref & {
39
-
// schemas.Hof
40
-
// #hof: env: {
41
-
// root: true // need to figure out what this really means, how it interacts with discovery & cli vs walking a CUE value to construct a giant dagger dag
0 commit comments